dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26052

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to 6.5.20.0 / 2024.3.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.19 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.19 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious JavaScript into form fields, which is then persisted on the server. When other users browse to pages containing these compromised form fields, the malicious script executes in their browsers.

MitigationUpgrade to a version newer than 6.5.19. Additionally, implement output encoding and input validation for all form fields to prevent XSS execution.

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.20.0< 2024.3.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. Identify if Adobe Experience Manager is installed
    Check for AEM by accessing the login page at /libs/granite/core/content/login.html or looking for 'Adobe Experience Manager' in the page source of the web application. AEM typically runs on port 4502 (author) or 4503 (publish).
    Affected if AEM is found running in the environment
  2. Determine the installed AEM version
    Navigate to the AEM Welcome page (/aem/start.html) and locate the version information typically displayed in the 'Version' field, or access /system/console/configMgr and check the version bundle. Alternatively, check the JAR file name in the installation directory.
    Affected if The installed version is less than 6.5.20.0 or less than 2024.3.0
  3. Verify form functionality is in use
    Check if AEM Forms module is enabled by navigating to /libs/fd/fm/view/formsmanager or by reviewing installed packages under /crx/packmgr. Forms are created using Adaptive Forms, Foundation Forms, or Core Components with form fields.
    Affected if Form creation and submission features are enabled and accessible to users
  4. Inspect form data repositories for suspicious content
    Query the AEM repository (CRXDE Lite at /crx/de) under /content/forms/af or /content/dam/formsanddocuments for any form submissions. Review stored field values for encoded or suspicious script tags such as <script>, javascript:, or onload/onerror attributes.
    Affected if Form data contains unsanitized user input with script tags or JavaScript event handlers

You are affected if AEM is running with a version below 6.5.20.0 or below 2024.3.0 and the Forms module is enabled with stored form submissions containing unsanitized content.

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.20.0 / 2024.3.0 or later
Fixed in 6.5.20.02024.3.0
Interim mitigation

Upgrade to a version newer than 6.5.19. Additionally, implement output encoding and input validation for all form fields to prevent XSS execution.

Recommended fix High confidence

AEM 6.5.20.0+ (on-premise) or AEM 2024.3.0+ (Cloud Service)

  1. Verify current Adobe Experience Manager version by navigating to Help > About Adobe Experience Manager or checking the system console (/system/console/bundles)
  2. For AEM 6.5.x on-premise installations: Schedule maintenance window and upgrade to AEM 6.5.20.0 or later
  3. For AEM as a Cloud Service / 2024 releases: Upgrade to 2024.3.0 or later via Cloud Manager
  4. After upgrade, validate that custom form components properly encode output to prevent reflected XSS
  5. Test by attempting to inject script content (e.g., <script>alert('XSS')</script>) into form fields to confirm vulnerability is remediated
  6. Clear AEM caches and publish updated content after verification
Caveat Standard AEM upgrade precautions apply - review release notes for deprecation notices, test custom code compatibility, and backup before upgrading

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
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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