Database data exposure via log_user SQL injection
Published Mar 12, 2026 · Updated Mar 12, 2026
SQL injection in 202CMS v10 beta allows remote attackers to read or modify database data through a crafted log_user POST value. The public proof of concept posts a time-delay SQL expression to index.php, while the vulnerable query construction itself is not publicly documented. No authentication or user interaction is required; successful exploitation exposes database confidentiality and permits limited modification.
Summary
What happened
SQL injection in 202CMS v10 beta allows remote attackers to read or modify database data through a crafted log_user POST value. The public proof of concept posts a time-delay SQL expression to index.php, while the vulnerable query construction itself is not publicly documented. No authentication or user interaction is required; successful exploitation exposes database confidentiality and permits limited modification.
The record
- CVE
- CVE-2019-25538
- Published
- Mar 12, 2026
- Updated
- Mar 12, 2026
- Vendor
- 202CMS
- Product
- 202CMS
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2026CVE publishedPublication date reported by the CVE source.
- Mar 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v10 beta
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- 202CMS v10beta Multiple SQL Injectionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo