dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-53964

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 6.5.22 / 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 a low privileged 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 · high confidence

Adobe Experience Manager versions 6.5.21 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged authenticated attacker can inject malicious JavaScript payloads into vulnerable form inputs, which persist in the system and execute when other users view the affected pages.

MitigationUpgrade Adobe Experience Manager to version 6.5.22 or later to obtain the vendor patch, or implement strict input validation and output encoding on all form fields as a compensating control.

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< 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. Determine installed AEM version
    Navigate to the AEM Welcome page or check the product info via the system console. The version is typically displayed on the AEMstart page under 'Welcome to Adobe Experience Manager' or accessible via the version info in the OSGi console.
    Affected if The installed version is 6.5.21 or earlier, OR the version is below 2024.11.0 (for the 2024 release track).
  2. Identify custom form components in use
    Review the AEM instance for any custom form components, adaptive forms, or form containers created using AEM Forms. Check the CRX/DE repository under /apps for custom form implementations.
    Affected if Custom or adaptive forms are present and the AEM version is within the affected range.
  3. Audit form field input validation configuration
    Examine the form field components in the CRX/DE Lite (accessible at /crx/de) for the input validation and output encoding settings. Look at the XML configuration of form components under /apps or /libs for properties related to validation patterns, allowed tags, or encoding.
    Affected if Form fields lack server-side input validation or output encoding is disabled, and the AEM version is affected.
  4. Check for suspicious content in form data repositories
    Review the repository content where form data is stored (typically under /content or custom form data nodes in CRX/DE). Look for script tags, javascript: URIs, or event handler attributes in form field values.
    Affected if Malicious script payloads are found stored in form data nodes within the repository.

You are affected if your AEM version is 6.5.21 or earlier, or is below 2024.11.0, and you have custom form components that accept user input without proper validation and encoding.

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

Upgrade Adobe Experience Manager to version 6.5.22 or later to obtain the vendor patch, or implement strict input validation and output encoding on all form fields as a compensating control.

Recommended fix High confidence

6.5.22 or 2024.11.0 (whichever release line is applicable)

  1. Upgrade Adobe Experience Manager to version 6.5.22 or later for the 6.5.x release line
  2. Alternatively, upgrade to version 2024.11.0 or later for the cloud-native release line
  3. After upgrade, verify the XSS vulnerability is resolved by testing form fields where malicious scripts were previously injectable
  4. Confirm that low-privileged users can no longer inject malicious scripts into vulnerable form fields
Caveat Review Adobe's release notes for the target version to check for any breaking changes or deprecations that may affect custom implementations

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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