JoomlaCMS
CVE-2007-6642
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 · uneditedMultiple cross-site request forgery (CSRF) vulnerabilities in Joomla! before 1.5 RC4 allow remote attackers to (1) add a Super Admin, (2) upload an extension containing arbitrary PHP code, and (3) modify the configuration as administrators 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 confidenceCross-site request forgery (CSRF) vulnerabilities in Joomla! before version 1.5 RC4 allow remote attackers to trick authenticated administrators into unknowingly performing privileged actions: adding a new Super Administrator account, uploading extensions containing malicious PHP code, and modifying system configuration settings.
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
JoomlaCMS
= 1.5rc4CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Identify Joomla installation versionLocate the version file in the Joomla installation, typically in /libraries/joomla/version.php or check the version displayed in the administrator login page. Alternatively, check the version string in the database if accessible.Affected if The installed version is any release before Joomla! 1.5 RC4 (e.g., 1.5 Beta, 1.5 Alpha, or 1.0.x series when using the 1.5 admin panel).
-
Confirm admin panel accessibilityVerify that the Joomla administrator panel (/administrator/) is accessible and exposed, as the CSRF vulnerability targets authenticated administrative sessions.Affected if The admin panel is publicly or internally accessible without additional network restrictions.
-
Check for existing admin accountsReview the list of Super Administrator accounts in the Joomla admin panel under 'Site > User Manager' or directly query the jos_users table (or prefix_users table) for users with Super Administrator group assignments.Affected if Unexpected or unauthorized Super Administrator accounts exist that were not created by legitimate administrators.
If the Joomla version is before 1.5 RC4 and the administrator panel is accessible, the environment is vulnerable to CSRF attacks allowing unauthorized admin account creation, extension uploads, and configuration changes.
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 to Joomla! 1.5 RC4 or later which includes anti-CSRF token validation for administrative actions; as an interim measure, educate administrators about not clicking untrusted links while logged into the admin panel.
Fix this in Joomla
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6642 — 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-2007-6642 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