dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-52862

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 in form fields. Attackers can inject malicious JavaScript into form input fields, which persists in the system and executes when legitimate users browse to pages containing the compromised fields.

MitigationApply Adobe security patch (AEM 6.5.22 or later) to address this vulnerability. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure.

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. Verify AEM version
    Navigate to Help > About Adobe Experience Manager in the AEM console, or inspect the version.properties file located in the crx-quickstart directory, to confirm the exact installed version number
    Affected if The installed version is below 6.5.22.0 (for 6.5.x releases) or below 2024.11.0 (for cloud/2024 releases)
  2. Identify deployed form components
    Review the Components console at /libs/fd/components or /libs/core/components to enumerate all adaptive form, core form components, or custom form components currently active in the system
    Affected if Any form components are installed and accessible to untrusted users for input
  3. Check form field output encoding configuration
    Inspect the XML configuration or HTL/Sightly template source code of active form components to verify whether output encoding (HTML escaping) is applied to field labels, placeholders, help text, and error messages
    Affected if Form field rendering templates do not apply HTML encoding to user-supplied input displayed on the page
  4. Examine stored form data for suspicious content
    Use CRXDE Lite or the Repository Browser to query form submission nodes under /content/forms and search for stored values containing script tags, javascript: protocols, or HTML event handlers such as onerror, onload, onmouseover
    Affected if Any form submission nodes contain encoded or raw script tags or event handler attributes indicating prior exploitation

The environment is affected if the installed AEM version is below 6.5.22.0 or below 2024.11.0 AND the system has form components that accept and display user input without proper output 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.0 / 2024.11.0 or later
Fixed in 6.5.22.02024.11.0
Interim mitigation

Apply Adobe security patch (AEM 6.5.22 or later) to address this vulnerability. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure.

Recommended fix High confidence

Adobe Experience Manager 6.5.22.0+ (6.5.x line) or 2024.11.0+ (Cloud/newer release line)

  1. Verify current Adobe Experience Manager version by accessing the AEM Welcome page or checking the version.properties file
  2. Plan and schedule maintenance window for the upgrade
  3. Backup the current AEM instance including repository, database, and configurations
  4. For AEM 6.5.x installations: Upgrade to version 6.5.22.0 or later
  5. For AEM as a Cloud Service / newer releases: Upgrade to version 2024.11.0 or later
  6. Run the upgrade following Adobe's official upgrade documentation for your specific version
  7. After upgrade, verify all AEM services start correctly
  8. Test the specific form fields that were vulnerable to confirm the XSS vulnerability is remediated
Caveat Review Adobe's release notes for 6.5.22.0 or 2024.11.0 for any compatibility changes; major version upgrades may require content migration or configuration updates

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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