dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-52836

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

MitigationUpgrade to AEM 6.5.22 or later to receive the security patch. As an interim measure, implement strict input validation and output encoding on vulnerable form fields, or deploy a WAF rule to filter 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. Check AEM version
    Navigate to the AEM Welcome page or access /system/console/configMgr and locate the Adobe Experience Manager version information. Alternatively, check the crx-quickstart/package.properties file for the version number.
    Affected if The installed version is earlier than 6.5.22.0 or earlier than the 2024.11.0 release.
  2. Identify Forms modules in use
    Access the AEM Forms interface at /aem/forms or inspect the Forms UI at /libs/fd/fp/extensions. Check if Adaptive Forms or Core Components with form functionality are deployed.
    Affected if Adobe Forms, Adaptive Forms, or Core Components form features are enabled and accessible to users.
  3. Inspect form data storage
    Use CRXDE Lite (accessible at /crx/de) or query the AEM repository under /content/dam/formsanddocuments or /content/forms/af to view stored form submissions and field data.
    Affected if Form field data exists in the repository without proper input validation filters applied.
  4. Review content security policies
    Check the Apache Sling referrer filter configuration at /system/console/configMgr/org.apache.sling.security.impl.ReferrerFilter and Content Security Policy headers in the dispatcher configuration. Look for any custom XSS protection rules.
    Affected if The CSP headers are weak or missing, and no output encoding is applied to form-rendered content.

You are affected if your AEM version is below 6.5.22.0 or below the 2024.11.0 release and Forms modules that accept user input are enabled in your environment.

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 to AEM 6.5.22 or later to receive the security patch. As an interim measure, implement strict input validation and output encoding on vulnerable form fields, or deploy a WAF rule to filter XSS payloads.

Recommended fix High confidence

Adobe Experience Manager 6.5.22.0 (for 6.5.x branch) or 2024.11.0 (for 2024.x branch)

  1. Identify your current Adobe Experience Manager version by checking the product console or system information
  2. If running 6.5.x branch (6.5.21 or earlier), schedule upgrade to version 6.5.22.0 or later
  3. If running 2024.x branch (2024.10 or earlier), schedule upgrade to version 2024.11.0 or later
  4. Review Adobe's official upgrade documentation for your specific version path
  5. Execute upgrade in a test/staging environment before production deployment
  6. Verify the upgrade completed successfully and the XSS vulnerability is resolved
Caveat Review Adobe's release notes for your specific upgrade path for any compatibility notes 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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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