dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26035

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 where malicious JavaScript can be injected into form fields and persists in the system, executing in victims' browsers when they view pages containing the affected fields.

MitigationUpdate Adobe Experience Manager to a version newer than 6.5.19, or implement strict input validation and output encoding on vulnerable form fields to prevent script injection.

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. Check Adobe Experience Manager version
    Access the AEM Welcome page or check the crx/com.sun.jmx.mbeanserver.MBeanSafeControl MBean via the Felix console at /system/console/mbeans, or query the version via the OSGi bundle console at /system/console/bundles
    Affected if Installed version is below 6.5.20.0 or below 2024.3.0 (for cloud/2024 releases)
  2. Identify custom form components
    Review the /apps directory in CRX/DE for custom form components, specifically Adaptive Form fragments, Core Components form fields, or custom form containers that accept user input and store data in the repository
    Affected if Custom or Core Components form fields are in use that do not have output encoding applied to submitted values
  3. Inspect form field data in repository
    Query the repository using CRXDE Lite (at /crx/de) or the Query Builder API to examine stored values in form-related content nodes (look in /content, /etc, or custom form model nodes) for suspicious script tags, JavaScript: URLs, or event handlers
    Affected if Form field data contains unsanitized HTML or script tags that could execute in a user's browser
  4. Check for Content Services or Form Data Model usage
    Review whether Forms Data Model (FDM), Adaptive Forms, or custom form submissions are configured to persist data without server-side validation - check /content/forms/af or similar paths
    Affected if Form data is persisted directly without input validation or output encoding applied before rendering

You are affected if your AEM version is below 6.5.20.0 (or below 2024.3.0 for cloud) AND you have form fields in use that store user input without proper sanitization.

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

Update Adobe Experience Manager to a version newer than 6.5.19, or implement strict input validation and output encoding on vulnerable form fields to prevent script injection.

Recommended fix High confidence

AEM 6.5.20.0 or AEM 2024.3.0

  1. Backup the current AEM instance and content repository before starting the upgrade process
  2. Review the Adobe Experience Manager upgrade documentation for the target version (6.5.20.0 or 2024.3.0)
  3. Test the upgrade in a non-production environment first to identify any compatibility issues
  4. Perform the upgrade following Adobe's recommended upgrade procedures for AEM as specified in the official documentation
  5. After upgrade, verify the AEM version is correct by navigating to Help > About Adobe Experience Manager
  6. Clear the AEM cache and rebuild any custom indexes if necessary
  7. Test that the XSS fix is working by verifying that malicious scripts cannot be injected into form fields
Caveat Review custom code and third-party integrations for compatibility with the new version before upgrading production

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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