dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-52849

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.21 and earlier allows attackers to inject malicious JavaScript into vulnerable form fields. When users view pages containing these compromised fields, the malicious script executes in their browsers.

MitigationUpgrade Adobe Experience Manager to version 6.5.22 or later. Implement strict input validation and output encoding 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. Check installed AEM version
    Navigate to the AEM Welcome page or check the product version through the system information console (typically at /system/console/bundles or /crx/packmgr/service.jsp). Compare the version number against the affected ranges: < 6.5.22.0 or < 2024.11.0
    Affected if The installed version is 6.5.21.0 or earlier, or falls between 6.5.22.0 and 2024.10.x (before 2024.11.0)
  2. Identify form components in use
    Review the AEM instance for pages that use Adaptive Forms, Form Fragments, or core form components. Check /libs/fd/af/ and /apps/fd/af/ directories for form-related content. Look for form models in the repository at /conf/global/settings/cloudconfigs/fdm/
    Affected if The AEM instance deploys and uses Adaptive Forms or other form components that accept user input
  3. Inspect form field data for suspicious content
    Query the repository (via CRXDE Lite at /crx/de or using the Query Manager) for form field content. Look for entries containing script tags, javascript:, onerror=, onload=, or other XSS payloads within form field values stored under /content/ or /etc/
    Affected if Form field data contains unsanitized HTML/script tags that could indicate exploitation or testing attempts
  4. Check form field input validation settings
    Review the form field validation rules in the Adaptive Form editor or form model configuration. Verify whether Strict Input Validation and Output Encoding are enabled on text fields, especially single-line text, multi-line text, and numeric fields
    Affected if Form fields lack strict input validation or output encoding is disabled, allowing script injection

A user is affected if their AEM version is below 6.5.22.0 (for 6.x releases) or below 2024.11.0, AND the instance uses form components with user input fields that lack proper validation and 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. Implement strict input validation and output encoding on form fields as a defense-in-depth measure.

Recommended fix Moderate confidence

Adobe Experience Manager 6.5.22.0 or 2024.11.0

  1. 1. Back up your current Adobe Experience Manager instance including the repository, database, and configurations
  2. 2. Review Adobe's official upgrade documentation for your target version (6.5.22.0 or 2024.11.0)
  3. 3. Test the upgrade in a staging environment before applying to production
  4. 4. Ensure all custom code and third-party integrations are compatible with the target version
  5. 5. Execute the upgrade following Adobe's recommended upgrade procedure
  6. 6. Verify the upgrade was successful and test critical functionality
  7. 7. Validate that the XSS vulnerability is resolved by confirming form fields properly sanitize input

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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