dbcve.org
Joomla\!Application · Joomla

CVE-2024-40743

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-20
Fix available
A fix is available. Upgrade to 3.10.17 / 4.4.6 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
The stripImages and stripIframes methods didn't properly process inputs, leading to XSS 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 confidence

The stripImages and stripIframes methods in the affected software fail to properly sanitize or process input, allowing malicious image or iframe tags with crafted payloads to bypass the stripping logic and execute as XSS vectors.

MitigationFix the stripImages and stripIframes methods to properly validate and sanitize all input before processing, ensuring no script execution is possible through manipulated image or iframe elements.

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:>= 3.0.0, < 3.10.17>= 4.0.0, < 4.4.6>= 5.0.0, < 5.1.3

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. Determine installed Joomla version
    Log into the Joomla Administrator dashboard and navigate to System > System Information > Joomla! Version, or check the /libraries/cms/version.php file for the VERSION constant.
    Affected if The version is 3.0.0 to 3.10.16, 4.0.0 to 4.4.5, or 5.0.0 to 5.1.2.
  2. Identify content filtering configuration
    Navigate to Users > Manage > Filter Groups in the Administrator panel, or check the com_content configuration in the database under the #__extensions table for filter_params.
    Affected if Content filtering with stripImages or stripIframes is enabled for any user group.
  3. Check if text filters are active
    Go to Content > Articles > click Options > Text Filters tab, or inspect the global configuration XML at /administrator/components/com_config/model/form/config.xml.
    Affected if Any text filter type other than 'No Filtering' is assigned to user groups.
  4. Verify stripIframes/stripImages plugin usage
    Check Plugins > Content - Clean Up (or similar content filtering plugins) for enabled status, or search the codebase for calls to stripImages() and stripIframes() methods.
    Affected if A content filtering plugin that uses these methods is published and active.

You are affected if your Joomla version falls within the vulnerable ranges AND content filtering with stripImages or stripIframes is enabled for any user group that can submit 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 3.10.17 / 4.4.6 / 5.1.3 or later
Fixed in 3.10.174.4.65.1.3
Interim mitigation

Fix the stripImages and stripIframes methods to properly validate and sanitize all input before processing, ensuring no script execution is possible through manipulated image or iframe elements.

Recommended fix High confidence

Joomla! 3.10.17 for 3.x branches; Joomla! 4.4.6 for 4.x branches; Joomla! 5.1.3 for 5.x branches

  1. Create a complete backup of the Joomla! site including files and database
  2. Log in to the Joomla! Administrator backend
  3. Navigate to System > Update > Joomla! Update (or use Components > Joomla Update in some versions)
  4. Check for updates and install the available update to the fixed version (3.10.17, 4.4.6, or 5.1.3 depending on your current major version)
  5. Alternatively, download the full upgrade package from downloads.joomla.org and install it via Extensions > Manage > Install
  6. Clear any Joomla! and server-side caches after upgrade
  7. Verify the stripImages and stripIframes methods now properly sanitize inputs by testing with XSS payloads
  8. Test critical site functionality to ensure the upgrade did not break existing features
Caveat Minor version upgrades within the same major version (e.g., 5.0.x to 5.1.3) typically have minimal breaking changes, but always review the Joomla! release notes for any deprecated features or backward-incompatible changes before upgrading

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

Fix this in Joomla\! Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40743 — 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-40743 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