Security readout for executives and security teams
Plain-English summary
202CMS v10 beta has an unauthenticated SQL injection flaw in the log_user parameter. An attacker could use it to read sensitive database data or alter database contents. The issue is high severity because it is remotely reachable and requires no login or user interaction.
Executive priority
Prioritize remediation for any internet-facing 202CMS v10 beta deployment. The business risk is database compromise without authentication. If the product is not in use, document non-exposure and monitor for future asset discoveries.
Technical view
CVE-2019-25538 is CWE-89 SQL injection in 202CMS v10 beta via log_user. The record lists CVSS 4.0 score 8.8 with network access, low complexity, no privileges, and no user interaction. Sources describe potential database disclosure and modification.
Likely exposure
Exposure is limited to organizations running 202CMS v10 beta, especially if internet-facing. The source bundle provides no CPEs and no broader affected-version range, so asset identification may require manual confirmation.
Exploitation context
A public ExploitDB entry exists, so exploit information is publicly available. The provided sources do not show CISA KEV listing or confirmed active exploitation. Attackers would need network access to a vulnerable 202CMS v10 beta instance.
Researcher notes
Evidence is limited to the CVE/advisory bundle and ExploitDB reference. No CPEs, patch version, or active exploitation confirmation are provided. Treat version scoping carefully and avoid assuming other 202CMS versions are affected.
Mitigation direction
- Identify any 202CMS v10 beta deployments, especially public-facing sites.
- Check 202CMS or hosting project guidance for a fixed release or official mitigation.
- If no maintained fix exists, remove exposure or migrate away from the beta version.
- Restrict access to affected application paths until remediation is complete.
- Review database and application logs for suspicious log_user activity.
Validation and detection
- Confirm whether 202CMS v10 beta is deployed in the environment.
- Verify internet exposure through asset inventory and external attack surface records.
- Check application code or request handling for log_user use in database queries.
- Review vendor and advisory references for updated affected-version or fix information.
- Monitor logs for anomalous requests targeting the vulnerable parameter.
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-25538 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 log_user ParameterCVE 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.