dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-52858

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

MitigationApply the vendor patch when available. Until then, implement input validation and output encoding on form fields, or disable/restring user access to vulnerable form components.

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
    Access the AEM Web Console Bundles page ( Navigate to /system/console/bundles or /system/console/status/productinfo ) and locate the 'Adobe Experience Manager' version entry, or check the Welcome page 'Version' field under 'Repository'
    Affected if Version is below 6.5.22.0 (for 6.5.x branch) or below 2024.11.0 (for cloud/2024 releases)
  2. Identify active form components
    Review your site content structure in CRX/DE Lite (navigate to /content) or use the AEM Forms UI to list all adaptive forms, core form components, or custom form implementations currently deployed
    Affected if Any form components (adaptive forms, core form components, or custom form fields) are actively in use on the system
  3. Inspect form field input validation settings
    Open form components in edit mode via the AEM Forms editor or edit the component dialog in the Edit dialog; examine each form field's 'Validation' tab or properties panel for presence of input validation rules (required, pattern, min/max length, custom validation)
    Affected if Form fields exist without configured input validation or pattern constraints, allowing arbitrary input to be stored
  4. Audit stored form submissions for unencoded content
    Query the repository for form submission data under /content/forms/af or custom form data paths in CRX/DE; examine stored values in form field nodes for presence of HTML tags, script elements, or JavaScript event handlers that should have been encoded
    Affected if Form submission nodes contain raw HTML, script tags, or event handler attributes (onclick, onerror, etc.) in field values

Your environment is affected if the installed AEM version is below 6.5.22.0 or below 2024.11.0 AND you have form components in use that accept user input without input 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

Apply the vendor patch when available. Until then, implement input validation and output encoding on form fields, or disable/restring user access to vulnerable form components.

Recommended fix High confidence

6.5.22.0 or 2024.11.0 (depending on which release train is in use)

  1. Upgrade Adobe Experience Manager from any version below 6.5.22.0 to version 6.5.22.0 or later for the 6.5.x release line
  2. If using the 2024 release train, upgrade to 2024.11.0 or later
  3. After upgrading, verify the stored XSS vulnerability is no longer present in form fields
  4. Test that malicious scripts cannot be injected into vulnerable form fields in the admin console

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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