Joomla\!Application · Joomla
CVE-2021-26029
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 · uneditedAn issue was discovered in Joomla! 1.6.0 through 3.9.24. Inadequate filtering of form contents could allow to overwrite the author field.
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 · high confidenceAn input validation vulnerability in Joomla! versions 1.6.0 through 3.9.24 allows attackers to overwrite the author field in form submissions due to inadequate filtering of form contents. This is a data integrity issue that permits manipulation of article authorship metadata.
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
Joomla\!Application
>= 1.6.0, < 3.9.25CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
-
Determine installed Joomla versionAccess the Joomla administrator backend and navigate to Help > System Information > Joomla! Version, or check the libraries/cms.php file for the VERSION constantAffected if The installed version is 1.6.0 through 3.9.24 (versions >= 1.6.0 and < 3.9.25)
-
Verify article submission is enabledIn the Joomla admin panel, go to Content > Articles and check if the Create permission is allowed for the relevant user groups, or inspect the #__assets table for com_content article permissionsAffected if Public or guest users have article creation permissions and the version is within the affected range
-
Identify com_content component statusCheck if the com_content component is published by querying the #__extensions table for extension_id where element = 'com_content' and enabled = 1Affected if The component is enabled and the Joomla version is vulnerable
-
Review recent article submissions for author field integrityQuery the #__content table for articles and compare the created_by field against the expected author, or inspect article submission logs for unexpected author valuesAffected if Articles exist where the created_by user ID does not match the intended submitter and the version is within the affected range
Your environment is affected if Joomla! version is 1.6.0 through 3.9.24 and article/form submissions are permitted on the site.
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 data3.9.25
Upgrade Joomla! to version 3.9.25 or later which contains the proper input filtering fix for this vulnerability.
Fix this in Joomla\!
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26029 — 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-2021-26029 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