dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-27224

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 6.5.24.0 / 2026.2.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.23 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.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where malicious JavaScript can be injected into form fields. The payload persists in the system and executes when users view pages containing the compromised fields.

MitigationUpdate Adobe Experience Manager to a version newer than 6.5.23. Additionally, implement proper input validation and output encoding on form fields to prevent XSS attacks.

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.24.0< 2026.2.0= 6.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. Check Adobe Experience Manager installed version
    Navigate to the AEM Welcome page or access /system/console/bundles.json, or run: curl -s http://localhost:4502/crx/packmgr/service.jsp?cmd=ls 2>/dev/null | grep -i 'version' . Alternatively, check the product.info in the OSGi console at /system/console/product.json
    Affected if The installed version is lower than 6.5.24.0, lower than 2026.2.0, or exactly 6.5
  2. Identify form field configurations
    Review form components in AEM Content Fragments or Adaptive Forms at /libs/fd/af/authoring/components and custom form configurations under /apps. Check for form field definitions in XML (.xml) or .form.js files
    Affected if Custom form fields or Adaptive Forms are configured with user input capabilities and no output encoding is applied
  3. Inspect stored form data for malicious scripts
    Query the AEM repository (CRX/DE) at /content or use Query Builder to search for stored form submissions: curl -s -u admin:admin 'http://localhost:4502/bin/querybuilder.json?path=/content&type=nt:unstructured&property=jcr:content/*' | grep -i '<script\|javascript:' or examine form data in the MongoDB or RDB datastore if external storage is used
    Affected if Any form submissions contain persisted script tags, javascript: URIs, or event handler attributes like onload/onerror
  4. Verify form input validation settings
    Check form field validation rules in the AEM Forms UI at /aem/forms/editor/content/editor.html or inspect the validation model in the form definition JSON at /conf/<project>/settings/wcm/template-types/adaptive-template
    Affected if Form fields lack server-side validation or XSS protection rules are disabled/missing

You are affected if AEM version is below 6.5.24.0 or below 2026.2.0 AND your AEM deployment uses form fields that accept and store user input without XSS protection.

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.24.0 / 2026.2.0 or later
Fixed in 6.5.24.02026.2.0
Interim mitigation

Update Adobe Experience Manager to a version newer than 6.5.23. Additionally, implement proper input validation and output encoding on form fields to prevent XSS attacks.

Recommended fix Moderate confidence

6.5.24.0 or later (or 2026.2.0+)

  1. 1. Back up your current Adobe Experience Manager instance and content repository
  2. 2. Review the Adobe Experience Manager 6.5.24.0 or 2026.2.0+ release notes for any migration requirements
  3. 3. Stop the AEM instance
  4. 4. Apply the upgrade following Adobe's standard upgrade procedure for your deployment type
  5. 5. After upgrade, verify that all custom code and integrations still function correctly
  6. 6. Test the specific form fields that were previously vulnerable to ensure the XSS fix is working
  7. 7. Restart the AEM instance and monitor for any errors
Caveat Review 6.5.24.0 release notes for breaking changes; some configurations or custom integrations may require updates

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-2026-27224 — 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-2026-27224 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