dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26061

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 · moderate confidence

Adobe Experience Manager versions 6.5.19 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where malicious scripts can be injected into vulnerable form fields. When users view pages containing these compromised fields, the embedded JavaScript executes in their browsers.

MitigationApply the vendor patch by upgrading to AEM 6.5.20 or later. Additionally, implement input validation and output encoding on all 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. Identify installed AEM version
    Access the AEM welcome page and navigate to 'Information' > 'Version' or append '/system/console/status-productinfo' to your AEM instance URL to view version details
    Affected if Installed version is below 6.5.20.0 or below 2024.3.0 (for cloud/flex releases)
  2. Confirm Forms module is in use
    Check if Adaptive Forms, Foundation Forms, or custom form components are enabled by navigating to /aem/forms in the AEM interface or reviewing installed form-related bundles in OSGi console at /system/console/bundles
    Affected if Forms functionality (Adaptive Forms, Foundation Forms) is installed and active on the instance
  3. Review form field configurations for injected scripts
    Navigate to CRXDE Lite (/crx/de) and search under /content/forms for any form field nodes (typically under /apps or /content) - inspect the 'value', 'label', or 'placeholder' properties for script tags or JavaScript event handlers
    Affected if Any form field nodes contain script tags (<script>), JavaScript event handlers (onclick, onerror, onload), or suspicious encoded content that could execute as XSS
  4. Audit form submission data for malicious payloads
    Check form submission folders in /content/forms/submissions or review the data stored in the form's submitted data store for any entries containing HTML tags, script elements, or JavaScript protocol handlers
    Affected if Form submission data contains unescaped HTML, script tags, or javascript: URLs stored in form fields

You are affected if your AEM version is below 6.5.20.0 or below 2024.3.0 AND you have Forms or Adaptive Forms enabled with form fields that could accept and 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

Apply the vendor patch by upgrading to AEM 6.5.20 or later. Additionally, implement input validation and output encoding on all form fields to prevent script injection.

Recommended fix High confidence

AEM 6.5.20.0 or later (on-premise); AEM as a Cloud Service 2024.3.0 or later

  1. 1. Identify current Adobe Experience Manager version by checking /system/console/systeminfo or AEM welcome page
  2. 2. Plan and schedule a maintenance window for the upgrade
  3. 3. Perform a full backup of the AEM instance including the content repository (CRX) and database
  4. 4. Upgrade Adobe Experience Manager to version 6.5.20.0 or later (for on-premise deployments)
  5. 5. Alternatively, if using cloud releases, upgrade to 2024.3.0 or later
  6. 6. After upgrade, verify the AEM instance starts successfully and all services are operational
  7. 7. Review Adobe's release notes for 6.5.20.0 to confirm the XSS vulnerability is addressed
  8. 8. Test the form fields that were previously vulnerable to ensure malicious scripts are now properly sanitized
Caveat Review Adobe Experience Manager 6.5.20.0 release notes for any breaking changes or migration requirements before upgrading

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-26061 — 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-26061 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