Security readout for executives and security teams
Plain-English summary
MODX Revolution 2.x through 2.5.6 has an authenticated blind SQL injection issue. A logged-in user may be able to query database data and possibly increase privileges. The supplied sources do not provide CVSS scoring, confirmed exploitation, or a named fixed version.
Executive priority
Treat as a priority upgrade and access-control review for any affected MODX sites. Business urgency is highest where many users can log in, accounts are externally exposed, or the site stores sensitive database content.
Technical view
The CVE attributes the flaw to improper sanitization in the xPDO escape method. The reported impact is authenticated database access with possible privilege escalation in MODX Revolution 2.x through 2.5.6. Evidence is limited to the CVE record and a MODX/xPDO changelog reference.
Likely exposure
Exposure is likely limited to MODX Revolution installations running 2.x through 2.5.6 where an attacker has valid user access. Internet-facing manager portals increase business risk but are not required by the source description.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The issue requires authentication, which lowers opportunistic exposure but still matters where untrusted, compromised, or low-privilege accounts exist.
Researcher notes
Public evidence is sparse: no CVSS vector, CWE mapping, exploit confirmation, or explicit fixed release is supplied. Do not assume unauthenticated exploitation. Focus validation on version, authenticated attack surface, role design, and vendor changelog confirmation.
Mitigation direction
- Identify MODX Revolution instances running 2.x through 2.5.6.
- Check MODX/xPDO changelog and vendor guidance for fixed upgrade paths.
- Restrict MODX authenticated access to trusted users only.
- Review user roles and remove unnecessary elevated permissions.
- Monitor application and database logs for unusual authenticated activity.
Validation and detection
- Confirm MODX Revolution version from application inventory or deployment records.
- Verify whether any affected instances use xPDO from the referenced vulnerable range.
- Review active accounts for untrusted, stale, or compromised users.
- Check vendor changelog before declaring an instance remediated.
- Document whether manager access is internet-facing or internally restricted.
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.
Database 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-2017-1000067 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/modxcms/revolution/blob/9bf1c6cf7bdc12190b404f93ce7798b39c07bc59/core/xpdo/changelog.txtCVE reference · x_refsource_CONFIRM
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.