dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-53960

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-10
Fix available
A fix is available. Upgrade to 6.5.22.0 / 2024.11.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Adobe Experience Manager versions 6.5.21 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable 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

Adobe Experience Manager versions 6.5.21 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where malicious JavaScript can be injected into form fields. The injected script persists on the server and executes in victim browsers when they navigate to pages containing the compromised form fields.

MitigationUpdate Adobe Experience Manager to version 6.5.22 or later to apply the security patch that addresses this stored XSS vulnerability.

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
Experience ManagerApplication
Affected:< 6.5.22.0< 2024.11.0

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Adobe Experience Manager version
    Navigate to the AEM Welcome page or check the crx-quickstart/app.properties file for the 'version' or 'crx.quickstart.version' property. You can also query the JMX console or use the versioninfo command-line tool.
    Affected if The installed version is less than 6.5.22.0 or less than 2024.11.0 (for cloud/continuous delivery)
  2. Identify forms that accept user input
    Review the AEM Forms implementation by accessing the Forms & Documents console at /aem/forms.html or inspecting the form models and adaptive form configurations stored under /content/forms/af in the CRX/DE repository.
    Affected if The environment uses AEM Forms with adaptive forms that accept user-submitted data in fields such as text inputs, text areas, or other form components
  3. Inspect form field data for malicious scripts
    Query the CRX/DE repository under /content/forms/af and examine stored form submissions in the repository or the AEM Forms datastore. Look for script tags, javascript: handlers, or HTML event attributes in field values.
    Affected if Form field data contains persisted JavaScript code, HTML tags, or event handlers that were not sanitized on input
  4. Review published content for injected scripts
    Check published pages containing forms at /editor.html and inspect the rendered HTML source. Use the CRX/DE Lite to search for submitted form data under /content/forms/submissions/ or the corresponding data store.
    Affected if Rendered form pages include unsanitized script content when viewed in a browser

A user is affected if their AEM installation version is below 6.5.22.0 or below 2024.11.0 AND the system has forms that accept user input where unsanitized data could be stored and rendered.

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 6.5.22.0 / 2024.11.0 or later
Fixed in 6.5.22.02024.11.0
Interim mitigation

Update Adobe Experience Manager to version 6.5.22 or later to apply the security patch that addresses this stored XSS vulnerability.

Recommended fix High confidence

6.5.22.0 or 2024.11.0 or later

  1. 1. Identify the current Adobe Experience Manager version in use by checking the AEM About page or system console
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Back up the current AEM instance including the repository, database, and configuration files
  4. 4. Download Adobe Experience Manager version 6.5.22.0 or 2024.11.0 (or later) from the official Adobe distribution or licensing portal
  5. 5. Follow Adobe's official upgrade documentation to perform the upgrade
  6. 6. After upgrade, verify the AEM instance is running correctly and all custom code/components function as expected
  7. 7. Validate that the XSS vulnerability is remediated by testing the previously vulnerable form fields
Caveat Review Adobe's release notes for compatibility notes; custom components may require testing for AEM version compatibility

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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