Security readout for executives and security teams
Plain-English summary
202CMS v10 beta has a high-severity database injection flaw. An unauthenticated attacker may manipulate login or registration-related database queries and potentially extract sensitive database information. The known affected product is a beta CMS release, so organizations should treat any exposed instance as urgent to identify and contain.
Executive priority
Prioritize quickly if 202CMS v10 beta is externally reachable or stores user, credential, or business data. Public exploit information raises operational risk, even without confirmed active exploitation. If the software is unused, unsupported, or beta-only, removal or migration is the cleanest risk reduction.
Technical view
CVE-2019-25539 is a CWE-89 blind SQL injection in 202CMS v10 beta involving the log_user parameter. The source bundle describes unauthenticated network access and time-based blind extraction potential. CVSS v4.0 is 8.8 high, with high confidentiality impact and low integrity impact.
Likely exposure
Exposure is most likely where 202CMS v10 beta is deployed and reachable over the web. The provided sources identify only Sourceforge 202CMS v10 beta as affected. No other versions or products are supported by the provided evidence.
Exploitation context
A public ExploitDB reference exists, indicating exploit knowledge is public. The source bundle does not show CISA KEV listing or cited evidence of active exploitation in the wild. Treat this as publicly exploitable, but not confirmed actively exploited from the provided sources.
Researcher notes
Evidence supports unauthenticated blind SQL injection in 202CMS v10 beta only. The bundle names ExploitDB and VulnCheck references but does not provide a vendor patch, fixed version, or KEV status. Avoid expanding affected scope beyond the listed beta release without additional evidence.
Mitigation direction
- Inventory and locate any 202CMS v10 beta deployments.
- Remove internet exposure for affected instances where possible.
- Check vendor or project guidance for any fixed release or migration path.
- If no supported fix exists, migrate away from the vulnerable beta release.
- Apply web access controls or WAF rules as compensating protection.
Validation and detection
- Confirm whether 202CMS v10 beta is present in asset inventories.
- Check if registration or index endpoints are publicly reachable.
- Review logs for suspicious requests involving the log_user parameter.
- Perform safe code review for unsanitized database use of log_user.
- Use non-destructive scanning only under authorized change controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-25539 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.8HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-46579CVE reference · exploit
- Official Product HomepageCVE reference · product
- VulnCheck Advisory: 202CMS v10 beta SQL Injection via register.phpCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.