dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-52859

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 · high confidence

Adobe Experience Manager versions 6.5.21 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. Attackers can inject malicious JavaScript into form input fields, which persists in the system and executes when users browse to pages containing those compromised fields.

MitigationUpgrade Adobe Experience Manager to version 6.5.22 or later to obtain the security patch. Alternatively, implement input validation and output encoding on vulnerable form fields to neutralize malicious script injection.

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. Identify the installed Adobe Experience Manager version
    Navigate to the AEM welcome page (http://hostname:port/aem/start.html) or access Help > About Adobe Experience Manager in the top menu. The version number is displayed on the welcome screen.
    Affected if The installed version is earlier than 6.5.22.0 or earlier than 2024.11.0 (for cloud/2024 releases)
  2. Check version via system console
    Access http://hostname:port/system/console/configMgr and look for the Product Info component, or check the version string in the bundles console at /system/console/bundles/.
    Affected if The version displayed is < 6.5.22.0 or < 2024.11.0
  3. Verify form field functionality is in use
    Review your AEM instance for any Adaptive Forms, Core Components with form elements, or custom form field implementations. Check Content Explorer for form container components under /content.
    Affected if The instance uses AEM Forms, Adaptive Forms, or any form components that accept user input in form fields.
  4. Inspect stored form data for potential XSS payloads
    Query the repository under /content/forms/af or relevant form data paths using CRXDE Lite (http://hostname:port/crx/de) or the Query Builder. Look for stored values containing script tags, javascript:, or event handlers.
    Affected if Any stored form data contains unsanitized HTML or script tags that could execute in a browser.

You are affected if your AEM version is earlier than 6.5.22.0 or 2024.11.0 AND your instance uses form functionality that accepts user input.

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

Upgrade Adobe Experience Manager to version 6.5.22 or later to obtain the security patch. Alternatively, implement input validation and output encoding on vulnerable form fields to neutralize malicious script injection.

Recommended fix High confidence

6.5.22.0 or later for AEM 6.5.x; 2024.11.0 or later for AEM as a Cloud Service

  1. Backup your AEM instance and database before proceeding with any upgrade
  2. Review the Adobe Experience Manager upgrade documentation for your current version
  3. Download Adobe Experience Manager 6.5.22.0 or the 2024.11.0 release from the Adobe distribution center
  4. Test the upgrade in a staging environment before applying to production
  5. Execute the upgrade following Adobe's documented upgrade procedures
  6. Verify the XSS vulnerability is resolved by attempting to inject scripts into form fields
  7. Deploy the validated upgrade to production environment
Caveat Review Adobe's release notes for your specific version for any breaking changes or migration requirements

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 / 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-52859 — 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-52859 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