dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-52846

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 that persists in the system and executes when victims browse to pages containing the compromised fields.

MitigationUpgrade Adobe Experience Manager to version 6.5.22 or later. Until patched, implement input validation on form fields and consider WAF rules to detect and block XSS payloads.

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. Determine your Adobe Experience Manager version
    Access the AEM welcome page and click 'Product Information' or navigate to /system/console/status-productinfo. Alternatively, check the version file in crx-quickstart/app.properties or view the version from the AEM About dialog (Help > About Adobe Experience Manager).
    Affected if The installed version is earlier than 6.5.22.0 or earlier than the November 2024 release (2024.11.0).
  2. Identify form fields in your AEM instance
    Search your content repository under /content for adaptive forms, form containers, or custom form components. Common paths include /content/forms/af, /content/dam/formsanddocuments, or custom form components under /apps or /libs.
    Affected if You have deployed or use any form functionality that accepts user input in fields such as text inputs, textareas, or other form elements.
  3. Inspect form field configurations for input validation
    Examine the form field component configurations in your content repository using CRXDE Lite (accessible at /crx/de) or by reviewing the XML or JSON configuration files for your form components. Check if the components enforce input validation or output encoding.
    Affected if Form fields lack proper input validation rules or do not encode output (for example, no restriction on special characters like <, >, or script keywords).
  4. Review stored form data for suspicious content
    Use CRXDE Lite or the Query Builder (at /libs/cq/search/content/querybuilder.html) to query form submission data. Search the repository for stored content containing script tags, javascript: URIs, or event handlers like onload, onerror, or onclick.
    Affected if Any stored form data contains malicious JavaScript payloads such as <script> tags or event handler attributes.

You are affected if your AEM version is below 6.5.22.0 or below 2024.11.0 AND you have form fields in use that accept user input without proper validation or 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

Upgrade Adobe Experience Manager to version 6.5.22 or later. Until patched, implement input validation on form fields and consider WAF rules to detect and block XSS payloads.

Recommended fix High confidence

AEM 6.5.22.0 or later; or AEM 2024.11.0 or later

  1. 1. Backup your current AEM instance and verify you have a complete restore point.
  2. 2. Download Adobe Experience Manager 6.5.22.0 (or later 6.5.x release) from the Adobe Distribution Package or Software Distribution portal.
  3. 3. Stop the AEM author and publish instances.
  4. 4. Install the updated AEM package on each instance using the Package Manager or command-line installation.
  5. 5. Verify the installation completed successfully by checking the AEM version in the About Adobe Experience Manager section.
  6. 6. Clear the AEM cache and rebuild any custom indexes if necessary.
  7. 7. Restart all AEM instances and verify core functionality works as expected.
  8. 8. Test that the XSS vulnerability is no longer exploitable in affected form fields.
Caveat Review Adobe's 6.5.22 release notes for any compatibility changes or deprecated features before upgrading

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-52846 — 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-52846 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