dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-47990

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 6.5.25.0 / 2026.5.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.24, LTS SP1, 2026.04 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low-privileged 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. Scope is changed.

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager affecting versions 6.5.24, LTS SP1, 2026.04 and earlier. Low-privileged attackers can inject malicious JavaScript into form fields that persists on the page and executes in victims' browsers when they view the affected content.

MitigationUpdate Adobe Experience Manager to version 6.5.24+, the patched LTS SP1 release, or 2026.04+ to remediate this stored XSS vulnerability.

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.25.0< 2026.5.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. Confirm AEM installation and identify running instance
    Check if AEM is running by querying processes or checking common AEM ports (4502 for author, 4503 for publish). Access the AEM welcome page at the root URL or check for AEM-specific directories in the filesystem.
    Affected if AEM instance is found running on the system
  2. Determine installed AEM version
    Access the AEM version information page at /system/console/status-abouts or check the version.properties file located in the crx-quickstart directory. Compare the displayed version against the affected ranges: < 6.5.25.0, < 2026.5.0, or = 6.5
    Affected if Installed version matches one of the affected ranges (any version < 6.5.25.0, any 6.5.x version, or any version < 2026.5.0)
  3. Identify accessible form components accepting user input
    Review the AEM Forms or Content Services configuration in the AEM UI. Check for publicly accessible form fields or user-generated content areas. Look for form containers in the siteadmin or assets console.
    Affected if Form components that accept user input are exposed to low-privileged or anonymous users
  4. Verify output encoding configuration on form fields
    Inspect the form field component configurations in AEM. Check the HTML output of form fields for proper encoding by submitting test input with script tags and viewing the rendered page source.
    Affected if Form fields allow raw HTML/script injection without proper output encoding or input validation being applied

A user is affected if they are running any AEM version matching the affected ranges and have form components accessible to users that lack 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.25.0 / 2026.5.0 or later
Fixed in 6.5.25.02026.5.0
Interim mitigation

Update Adobe Experience Manager to version 6.5.24+, the patched LTS SP1 release, or 2026.04+ to remediate this stored XSS vulnerability.

Recommended fix High confidence

AEM 6.5.25.0 or later, or AEM 2026.5.0 or later

  1. 1. Identify the current Adobe Experience Manager version by checking the AEM welcome page or system console
  2. 2. Plan for upgrade during a maintenance window with proper backups
  3. 3. Backup the current AEM instance including repository, database, and configuration files
  4. 4. Review Adobe's official upgrade documentation for AEM 6.5.25 or the 2026.5.0 release
  5. 5. Execute the upgrade following Adobe's recommended upgrade procedure for your deployment type (single server or cluster)
  6. 6. Verify the upgrade was successful by checking the version in the AEM welcome page
  7. 7. Test critical workflows and forms to ensure functionality is intact after upgrade
  8. 8. Clear browser caches and test that the XSS fix is working by attempting to inject script in the previously vulnerable form fields
Caveat Review Adobe's release notes for 6.5.25.0 for potential compatibility issues with custom components or third-party integrations; major upgrades may require code adjustments

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