Security readout for executives and security teams
Plain-English summary
CVE-2026-1105 is a remotely reachable SQL injection in EasyCMS versions up to 1.6. A public proof-of-concept is reported, and the vendor reportedly did not respond. Organizations using EasyCMS should treat internet-facing instances as a priority because database confidentiality, integrity, and availability may be affected.
Executive priority
High priority for any organization running EasyCMS, particularly public-facing systems. The vulnerability is unauthenticated, remote, and has public exploit information. If EasyCMS is not in use, no direct action is required beyond confirming asset inventory.
Technical view
The issue affects unknown code in /UserAction.class.php where manipulation of the _order argument can lead to SQL injection. The CVSS v2 score is 7.5 with network access, low complexity, and no authentication required. Public exploit availability is reported, but the provided sources do not confirm active exploitation.
Likely exposure
Exposure is limited to organizations running EasyCMS 1.0 through 1.6, especially if the application is reachable from the internet. The affected CPE covers EasyCMS broadly, but the source bundle names versions 1.0 to 1.6.
Exploitation context
Sources state the attack can be executed remotely and that a public exploit or proof-of-concept exists. CISA KEV status is false in the supplied data, and no cited source confirms active exploitation in the wild.
Researcher notes
Evidence comes mainly from VulDB and the CVE record. The affected code path is described only as unknown code in /UserAction.class.php. No patch, fixed version, or vendor workaround is provided in the supplied sources. Avoid assuming exploitation beyond public proof-of-concept availability.
Mitigation direction
- Inventory EasyCMS deployments and confirm whether versions 1.0 through 1.6 are present.
- Check vendor or project guidance for an official fix or maintained replacement.
- Restrict public access to EasyCMS where business requirements allow.
- Apply compensating controls to monitor or block suspicious SQL injection patterns.
- Back up and review databases before making remediation changes.
Validation and detection
- Confirm whether /UserAction.class.php exists in deployed EasyCMS instances.
- Verify the running EasyCMS version against the affected 1.0 through 1.6 range.
- Review web and application logs for suspicious _order parameter activity.
- Check vulnerability management tools for CVE-2026-1105 coverage.
- Document any internet-facing EasyCMS systems for remediation tracking.
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-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCWE-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-2026-1105 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
- 7.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
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.
AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR106.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
7.5HighVector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-341697 | EasyCMS UserAction.class.php sql injectionCVE reference · vdb-entry, technical-description
- VDB-341697 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #731465 | https://github.com/TeamEasy/EasyCMS EasyCMS v1.6 SQL injection vulnerabilityCVE reference · third-party-advisory
- https://github.com/ueh1013/VULN/issues/15CVE reference · exploit, issue-tracking
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 in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.