dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-52827

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. An authenticated attacker can inject malicious JavaScript payloads into form inputs, which persist in the system. When legitimate users later browse to pages containing these compromised form fields, the malicious script executes in their browsers, potentially stealing session cookies or performing actions on behalf of the victim.

MitigationApply Adobe security patch for AEM 6.5.22 or later to address the vulnerability. Additionally, implement Content Security Policy (CSP) headers and ensure proper output encoding is applied to all user-supplied data rendered in form fields.

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 installed AEM version
    Navigate to AEM Welcome page > Tools > Operations > Diagnosis, or access /system/console/systeminfo to retrieve the product version. Alternatively, check the manifest.json file in the crx-quickstart folder.
    Affected if The installed version is below 6.5.22.0 or below 2024.11.0 (Cloud).
  2. Identify form components in use
    Review the content structure under /content for pages containing Adaptive Form components (af-core), Form Container (guideContainer), or custom form field components. Use CRXDE Lite to browse /libs or /apps for form-related components.
    Affected if Custom or out-of-the-box form components that do not apply output encoding to user input are present in the content tree.
  3. Inspect stored form field values for unencoded content
    In CRXDE Lite, navigate to content pages under /content that contain form data. Query the repository using XPATH or JCR SQL2 to search for form field node values that contain HTML tags or script elements, such as <script>, javascript:, or event handlers like onload/onerror.
    Affected if Form field nodes contain raw HTML or JavaScript code that is not entity-encoded.
  4. Review audit logs for injection attempts
    Access the AEM error log at crx-quickstart/logs/error.log or the audit log at var/audit/com.day CQ-replication.log. Search for entries containing suspicious patterns like <script, alert(, javascript:, or HTML tags within form submission parameters.
    Affected if Audit logs contain form submissions with malicious script payloads or HTML injection attempts.

A user is affected if their AEM installation version is below 6.5.22.0 (6.5.x line) or below 2024.11.0 (Cloud), AND they have form fields that accept user input and render that input back without proper 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 for AEM 6.5.22 or later to address the vulnerability. Additionally, implement Content Security Policy (CSP) headers and ensure proper output encoding is applied to all user-supplied data rendered in form fields.

Recommended fix High confidence

Adobe Experience Manager 6.5.22.0 (on-prem) or 2024.11.0 (flush/cloud releases)

  1. Identify your current Adobe Experience Manager version and track (6.5.x on-prem or 2024.x cloud/flush releases)
  2. For 6.5.x on-prem releases: Plan upgrade to version 6.5.22.0 or later
  3. For 2024 releases: Plan upgrade to version 2024.11.0 or later
  4. Schedule maintenance window for the upgrade following Adobe's official upgrade documentation
  5. Perform upgrade in staging/test environment first to validate compatibility
  6. After upgrading, verify that the XSS vulnerability is resolved by testing form field inputs with malicious script payloads
  7. Deploy the upgraded version to production
Caveat Review Adobe's release notes for 6.5.22.0 and 2024.11.0 for any compatibility or deprecation notices 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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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