CVE-2026-1105
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was identified in EasyCMS up to 1.6. This vulnerability affects unknown code of the file /UserAction.class.php. Such manipulation of the argument _order leads to sql injection. The attack can be executed remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in EasyCMS up to version 1.6 in the UserAction.class.php file via the _order parameter. The vulnerability allows remote attackers to manipulate SQL queries through unsanitized input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if EasyCMS is installedLook for EasyCMS installation directories or check web application inventory. Common paths include /admin, /cms, /easycms, or check for 'EasyCMS' string in application bannerAffected if EasyCMS is present on the server
-
Determine installed EasyCMS versionCheck version file in EasyCMS installation directory, typically version.php, about.php, or check meta tags/footer for version displayAffected if Version is 1.6 or lower (any version up to and including 1.6)
-
Locate UserAction.class.php fileSearch for UserAction.class.php in the application source code, typically in /include, /class, or /action directoriesAffected if UserAction.class.php file exists in the installation
-
Verify _order parameter usage in UserAction.class.phpOpen UserAction.class.php and search for occurrences of _order parameter. Check if this parameter is used in SQL queries without proper sanitization or parameterizationAffected if _order parameter is used in dynamic SQL queries without prepared statements or input validation
-
Confirm remote access to vulnerable endpointTest if the UserAction endpoint accepting _order parameter is accessible via HTTP requests without authentication requirementsAffected if The vulnerable parameter can be reached remotely
A user is affected if EasyCMS version 1.6 or lower is installed and the UserAction.class.php file processes the _order parameter in SQL queries without sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedReplace dynamic SQL queries with parameterized statements/prepared statements and implement proper input validation on the _order parameter to prevent SQL injection attacks.
- Disable the affected EasyCMS application immediately if possible, or place it behind a web application firewall (WAF) to mitigate SQL injection attacks.
- If the application is still needed, review the /UserAction.class.php file and implement input validation/sanitization on the _order parameter to prevent SQL injection.
- Consider migrating to an actively maintained CMS solution as EasyCMS appears abandoned (vendor did not respond to disclosure).
- Monitor for any security updates from the original vendor.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1105 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data