Security readout for executives and security teams
Plain-English summary
Subrion CMS versions before 4.1.6 contain a SQL injection flaw in a front-end action handler. If a vulnerable site is reachable, an attacker may be able to manipulate database queries. The sources do not provide CVSS, confirmed impact details, or active exploitation evidence.
Executive priority
Treat this as a priority remediation item for any public Subrion CMS deployment. SQL injection can create serious data exposure risk, but urgency depends on whether vulnerable versions are present and reachable.
Technical view
CVE-2017-11445 is described as SQL injection in /front/actions.php through POST data in Subrion CMS before 4.1.6. The source bundle does not include CVSS, CWE mapping, affected CPEs, or detailed exploitability constraints. KEV status is false.
Likely exposure
Exposure is most likely for internet-facing Subrion CMS installations running versions earlier than 4.1.6. The provided affected-product metadata is incomplete, so teams should confirm product/version inventory directly.
Exploitation context
No active exploitation is cited in the provided sources, and the CVE is not listed as KEV in the bundle. Public details indicate the vulnerable surface is a POST-handling front-end PHP endpoint, but the bundle does not provide safe reproduction details.
Researcher notes
The record is sparse: no CVSS, CWE, CPE, exploit status, or detailed impact is included. Analysis should stay bounded to Subrion CMS before 4.1.6 and the /front/actions.php POST handling described by the CVE and linked issue.
Mitigation direction
- Upgrade Subrion CMS to 4.1.6 or later where applicable.
- Review the linked vendor issue for project-specific guidance.
- Prioritize public Subrion sites and systems handling sensitive database content.
- Back up the site and database before applying CMS updates.
- Monitor POST traffic to /front/actions.php for suspicious database error patterns.
Validation and detection
- Inventory all Subrion CMS installations and record their versions.
- Confirm whether any instance is older than 4.1.6.
- Check whether /front/actions.php is present and reachable on deployed sites.
- Review web and application logs for unusual POST activity to that endpoint.
- Verify the application runs normally after upgrade or remediation.
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-11445 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/intelliants/subrion/issues/480CVE 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.