CVE-2010-4404
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 · uneditedSQL injection vulnerability in the Yannick Gaultier sh404SEF component before 2.1.8.777 for Joomla! allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
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 the sh404SEF Joomla! extension allows remote attackers to execute arbitrary SQL commands through unsanitized input. The vulnerability exists in versions prior to 2.1.8.777 and can be exploited without authentication, potentially allowing attackers to access, modify, or delete database contents.
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<= 2.1.7.761= 1.5.2.255= 1.5.3.296= 1.5.4.302= 1.5.5.388= 1.5.6.398= 1.5.7.407= 1.5.8.432= 1.5.9.434= 1.5.10.446= 1.5.11.459= 1.5.12.464CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 sh404SEF is installedAccess Joomla! administrator panel, navigate to Extensions > Install/Uninstall or Extensions > Manage, and search for 'sh404SEF' or 'sh404sef' to verify the component is presentAffected if The sh404SEF component appears in the installed extensions list
-
Identify installed versionIn Joomla! administrator, go to Components > sh404SEF (or check the extension details in Extensions > Manage) and locate the version number displayedAffected if Version is 2.1.7.761 or lower, or matches any of these: 1.5.2.255, 1.5.3.296, 1.5.4.302, 1.5.5.388, 1.5.6.398, 1.5.7.407, 1.5.8.432, 1.5.9.434, 1.5.10.446, 1.5.11.459, 1.5.12.464
-
Verify component is activeIn Joomla! administrator, navigate to Extensions > Manage > Manage, find sh404SEF, and confirm the Status column shows 'Enabled' or a green checkmarkAffected if The sh404SEF component is enabled and running on the site
-
Check for public-facing accessVisit your site homepage and inspect whether SEF URLs are being generated (sh404SEF typically rewrites URLs). Also check if the /administrator endpoint is accessible without requiring login for component queriesAffected if The site uses sh404SEF for URL rewriting and the component handles requests without authentication
You are affected if sh404SEF is installed, enabled, and the version number matches 2.1.7.761 or below, or any of the specific 1.5.x versions listed (1.5.2.255 through 1.5.12.464), since the SQL injection can be exploited remotely without authentication in those versions.
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 dataUpgrade sh404SEF component to version 2.1.8.777 or later. If immediate patching is not possible, consider disabling the component or implementing WAF rules to filter malicious SQL payloads.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-4404 — 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-2010-4404 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