dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26121

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 6.5.21 / 2024.5 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.20 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.20 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where malicious JavaScript can be injected into form fields and persisted in the system. When users view pages containing the compromised form fields, the malicious script executes in their browsers.

MitigationApply the AEM security patch (version 6.5.21 or later) and review affected form components for proper input validation and output encoding to prevent XSS.

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.21< 2024.5

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 AEM version
    Access the AEM welcome page or navigate to Help > About Adobe Experience Manager. Alternatively, check the version.properties file in the crx-quickstart folder or the product info in the system console (/system/console/bundles).
    Affected if The installed version is below 6.5.21 or below the 2024.5 release track.
  2. Identify form components in use
    Review the AEM instance for any forms created using AEM Forms, Adaptive Forms, or custom form components that accept and store user input.
    Affected if Form components that accept user input are deployed and accessible to content authors or end users.
  3. Inspect form field configurations
    Open the form component dialogs in AEM and check the Allowed Parents/Children settings, and verify whether input validation and output encoding options are configured.
    Affected if Form fields allow unrestricted text input without validation constraints or output encoding is disabled.
  4. Review stored form submissions
    Check the form submission data repository (in AEM Forms, review submitted data in thecrx-repository under /content/forms/fpdata or similar submission folders) for any unexpected script tags or JavaScript in field values.
    Affected if Form submission records contain unescaped HTML or JavaScript code in form field values.
  5. Audit content pages referencing forms
    Preview or view pages containing forms as an end user would see them, then inspect the page source to verify if user-supplied form data is rendered with proper HTML encoding.
    Affected if User-provided values in form fields display without proper encoding (e.g., script tags appear as literal text rather than being escaped).

The environment is affected if the installed AEM version is below 6.5.21 (or below 2024.5) AND the system uses form components that accept user input without proper input validation and 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.21 / 2024.5 or later
Fixed in 6.5.212024.5
Interim mitigation

Apply the AEM security patch (version 6.5.21 or later) and review affected form components for proper input validation and output encoding to prevent XSS.

Recommended fix High confidence

Adobe Experience Manager 6.5.21 or 2024.5

  1. Review the Adobe Experience Manager upgrade documentation for your current version
  2. Plan and schedule the upgrade during a maintenance window
  3. Back up your AEM instance including the repository, database, and configurations
  4. Ensure your environment meets the system requirements for the target version (6.5.21 or 2024.5)
  5. Upgrade Adobe Experience Manager to version 6.5.21 or later, or to version 2024.5 or later
  6. After upgrade, verify that the XSS protection filters are functioning correctly
  7. Test critical workflows and forms to ensure functionality is intact
  8. Deploy to production after successful testing
Caveat Review Adobe's release notes for potential compatibility issues with custom code or third-party integrations

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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