Pro3W CMS 1.2.0 SQL injection enables unauthorized admin access
Pro3W CMS version 1.2.0 contains an unauthenticated SQL injection vulnerability allowing attackers to bypass authentication and gain administrative access.
Sourcecert.pl — open the original
What to check
- Applies to
- The 1 CVE named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
CERT Polska coordinated the disclosure of CVE-2025-15498, a SQL injection vulnerability in Pro3W CMS software. The flaw exists in the login form where improper input neutralization allows unauthenticated attackers to bypass authentication mechanisms and obtain administrative privileges. The vulnerability was confirmed in version 1.2.0, though the exact affected version range remains undetermined due to lack of vendor response.
The vulnerability represents a critical risk as it combines unauthenticated access with the ability to escalate to full administrative control through a common attack vector. SQL injection in authentication forms is a well-understood attack pattern that can be readily exploited by attackers with basic technical skills.
The vendor has not responded to disclosure efforts, though CERT Polska indicates versions released in January 2026 and later should address the issue. Organizations running Pro3W CMS should immediately verify their version and update to the latest release if available. The vulnerability was responsibly reported by security researcher Jacek Czepil.
Mentioned in this report
Detection guidance
Possible SQL Injection Attempt Against CMS Login Form
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Detects common SQL injection meta-characters/tokens submitted to login or authentication endpoints, consistent with unauthenticated SQLi auth-bypass exploitation such as CVE-2025-15498 in Pro3W CMS. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Possible SQL Injection Attempt Against CMS Login Form
logsource:
category: webserver
detection:
selection_path:
cs-uri-stem|contains:
- login
- signin
- auth
selection_sqli:
cs-uri-query|contains:
- ''' OR '''
- ''' OR 1=1'
- 1=1--
- UNION SELECT
- UNION ALL SELECT
- admin'--
- ''' --'
- sleep(
- benchmark(
- xp_cmdshell
condition: selection_path and selection_sqli
fields:
- c-ip
- cs-uri-stem
- cs-uri-query
- cs-method
- sc-status
falsepositives:
- Security scanners or penetration testing tools deliberately probing login forms
- Automated vulnerability assessment / QA fuzzing of authentication endpoints
level: high
tags:
- attack.t1190
- attack.initial-access
id: f0190adf-54f3-5072-a509-6c8e19772673
status: experimental
author: Vorant
Administrative Authentication Success Immediately Following Suspicious Login Request
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Flags an HTTP response indicating successful authentication or redirection to an administrative panel occurring in the same request/session as SQL injection style payload in login parameters, suggesting authentication bypass via SQLi. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Administrative Authentication Success Immediately Following Suspicious Login
Request
logsource:
category: webserver
detection:
selection_sqli_payload:
cs-uri-query|contains:
- ''' OR '''
- ''' OR 1=1'
- admin'--
- UNION SELECT
selection_admin_success:
cs-uri-stem|contains:
- /admin
- /dashboard
- /panel
sc-status:
- 200
- 302
condition: selection_sqli_payload and selection_admin_success
falsepositives:
- Legitimate administrators whose credentials happen to contain apostrophes or SQL-like
characters (rare)
- Vulnerability scanners validating the SQLi finding as part of authorized testing
level: high
tags:
- attack.t1078
- attack.initial-access
- attack.stealth
id: f65c78ed-a233-5e86-8073-51dff873393c
status: experimental
author: Vorant
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://cert.pl/en/posts/2026/02/CVE-2025-15498
Free public brief. The detections with Splunk SPL already written (plus Elastic and KQL where they apply) are in the app with a free account, no card. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply) and live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,433 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs