dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-52848

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 vulnerable form inputs, which persists in the system and executes when other users browse to pages containing the affected fields.

MitigationUpgrade AEM to version 6.5.22 or later. Additionally, implement input validation and output encoding on all form fields to prevent XSS attacks.

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 your Adobe Experience Manager version
    Access the AEM Welcome page or use the system console at /system/console/system to view the installed AEM version. Look for the version number in the About Adobe Experience Manager information.
    Affected if The installed version is below 6.5.22.0 or below 2024.11.0 (if on the 2024 quarterly release track).
  2. Identify form field components in use
    Review your AEM instance for form components (such as those from the Core Components library or Foundation Form components) that are included in published content pages. Check the CRX/DE repository under /apps or /content for form-related components that accept user input.
    Affected if Form components that accept and store user input are present in your published content tree.
  3. Inspect stored form data for unencoded content
    Query the repository or database where form submissions are stored (typically under /content/usergenerated or the specific form container path in CRX). Examine stored field values for the presence of HTML tags, script elements, or JavaScript event handlers that could indicate injected code.
    Affected if Form submission storage locations contain raw HTML, script tags, or JavaScript code without sanitization.
  4. Review published pages rendering form fields
    Navigate to published pages that display form field values or form submission results. Use browser developer tools to inspect the HTML output and verify if form field values are rendered with proper output encoding (e.g., escaped < > & characters).
    Affected if Form field values are rendered as raw HTML or JavaScript in page output without encoding.

You are affected if your AEM version is below 6.5.22.0 (or below 2024.11.0) AND your published pages contain form fields that accept and display user input without proper sanitization.

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 AEM to version 6.5.22 or later. Additionally, implement input validation and output encoding on all form fields to prevent XSS attacks.

Recommended fix High confidence

AEM 6.5.22.0 or later, or AEM 2024.11.0 or later

  1. Review the Adobe Experience Manager upgrade documentation for your current version
  2. Plan and schedule the upgrade during a maintenance window
  3. Backup your AEM instance and content repository before upgrading
  4. For AEM 6.5.x users: Upgrade to version 6.5.22.0 or later
  5. For AEM cloud or 2024.x users: Upgrade to version 2024.11.0 or later
  6. After upgrade, verify that the XSS filter configurations are properly applied
  7. Test the upgraded environment to confirm the vulnerability is remediated
Caveat Review Adobe AEM 6.5.22 and 2024.11.0 release notes for potential breaking changes specific to your instance configurations

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