dbcve.org
Joomla\!Application · Joomla

CVE-2024-21729

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 4.4.6 / 5.1.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Inadequate input validation leads to XSS vulnerabilities in the accessiblemedia 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 · moderate confidence

Cross-site scripting (XSS) vulnerability in the accessiblemedia field due to inadequate input validation. User-supplied content in the accessiblemedia field is not properly sanitized or encoded before being rendered, allowing injection of malicious scripts.

MitigationImplement proper input validation and output encoding for the accessiblemedia field. Sanitize or escape any user-controlled content before rendering it in the browser.

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
Affected:>= 4.0.0, < 4.4.6>= 5.0.0, < 5.1.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Joomla core version
    Navigate to System > Information > Joomla! Information in the admin panel, or check the /libraries/cms/version.php file for the VERSION constant, or run: grep -r 'VERSION' /libraries/src/Version.php 2>/dev/null
    Affected if The version is >= 4.0.0 and < 4.4.6, OR >= 5.0.0 and < 5.1.2
  2. Identify accessiblemedia field usage in custom extensions
    Search XML manifest files and PHP field definitions for 'accessiblemedia': grep -r 'type="accessiblemedia"' /administrator/components/ /components/ /plugins/ 2>/dev/null
    Affected if Any custom component, plugin, or module uses the accessiblemedia field type
  3. Check custom templates for accessiblemedia integration
    Search template XML and PHP files for accessiblemedia references: grep -r 'accessiblemedia' /templates/ /administrator/templates/ 2>/dev/null
    Affected if A custom template has integrated the accessiblemedia field
  4. Review form definitions using accessiblemedia
    Examine forms.xml or config.xml files in extensions for <field type="accessiblemedia"> entries: find / -name "*.xml" -exec grep -l "accessiblemedia" {} \; 2>/dev/null | head -20
    Affected if Any XML form definition includes the accessiblemedia field type

You are affected if your Joomla version falls within the vulnerable ranges AND any extension, template, or custom code implements the accessiblemedia field to accept user-supplied content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.4.6 / 5.1.2 or later
Fixed in 4.4.65.1.2
Interim mitigation

Implement proper input validation and output encoding for the accessiblemedia field. Sanitize or escape any user-controlled content before rendering it in the browser.

Recommended fix High confidence

Joomla! 4.4.6 or Joomla! 5.1.2

  1. Backup your Joomla! site before upgrading
  2. Download Joomla! 4.4.6 (if on Joomla 4.x) or Joomla! 5.1.2 (if on Joomla 5.x) from the official Joomla! downloads page
  3. Upload and install the update through Joomla!'s built-in updater or replace files manually
  4. Verify the upgrade was successful by checking the backend version information
  5. Clear any caching systems in place
  6. Test the accessiblemedia field functionality to confirm the XSS fix is working

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Joomla\! Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21729 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21729 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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