CVE-2026-7389
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 security vulnerability has been detected in EyouCMS up to 1.7.9. The affected element is the function GetSortData of the file application/common.php. The manipulation of the argument sort_asc leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
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 EyouCMS up to 1.7.9 in the GetSortData function within application/common.php. The sort_asc parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL commands. This is a high-severity (CVSS 7.3) flaw that can be exploited remotely using publicly available exploit code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Confirm EyouCMS installation existsSearch the web root for EyouCMS files, typically in the application/ directory. Look for common EyouCMS index files or the presence of the application folder structure.Affected if EyouCMS is installed on the server
-
Identify installed EyouCMS versionCheck for a version file or header in common locations such as /data/conf/version.php, /application/extend/EyouCMS.class.php, or review the index.php for version constants. Compare the found version number against the affected range of up to 1.7.9.Affected if Installed version is 1.7.9 or lower
-
Locate vulnerable file application/common.phpNavigate to the web root and verify the existence of application/common.php. Open the file and search for the function definition 'function GetSortData'.Affected if The GetSortData function exists in application/common.php
-
Verify sort_asc parameter handlingReview the GetSortData function code to confirm it accepts a 'sort_asc' parameter. Look for any direct use of this parameter in SQL queries without sanitization or use of parameterized queries.Affected if The function processes sort_asc directly into SQL without prepared statements or escaping
-
Confirm endpoint accessibilityIdentify which controller or route invokes GetSortData. Test if HTTP requests with a sort_asc parameter can reach this function through common EyouCMS URLs such as list pages or API endpoints.Affected if The vulnerable function is accessible via HTTP and processes user-supplied sort_asc input
A user is affected if EyouCMS version 1.7.9 or lower is installed and the application/common.php file contains a GetSortData function that handles the sort_asc parameter without SQL 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.
From vendor dataSince the vendor has not issued a patch, organizations should immediately restrict network access to affected endpoints, implement WAF rules to filter malicious sort_asc input, or temporarily disable the vulnerable function until a fix is available from the vendor.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7389 — 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-7389 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