dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-47974

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

Adobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier contain a stored XSS vulnerability where low-privileged users can inject malicious JavaScript into form fields. The malicious payload persists in the system and executes in victims' browsers when they view the affected page. The scope change indicates the vulnerability impacts resources beyond the vulnerable AEM component.

MitigationUpgrade to the latest AEM version or apply the vendor-provided patch. Implement output encoding and input validation on affected form fields as an additional defense layer.

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. Locate AEM version information
    Access the AEM System Information console at /system/console/status-productinfo or check the crx-quickstart/etc/version.properties file for the product version string
    Affected if The displayed version is < 6.5.25.0 for 6.5.x releases, < 2026.5.0 for 2026.x releases, or exactly 6.5 without any service pack applied
  2. Confirm AEM release track
    Identify whether the installation is on the LTS (6.5.x) or quarterly (2026.x) release track by reviewing the version number format
    Affected if The version indicates 6.5.x without reaching 6.5.25.0, or a 2026.x release before 2026.5.0
  3. Verify service pack status
    In the AEM Package Manager at /crx/packmgr/list.jsp, review installed service packs and compare against version 6.5.25 (LTS SP2) or confirm no cumulative fix pack reaching 6.5.25 is installed
    Affected if No service pack at version 6.5.25 or later is installed on a 6.5 base release, leaving the version vulnerable
  4. Identify exposed form components
    Review form field components in AEM authored pages that accept user input, particularly those without explicit output encoding or custom validation rules
    Affected if Form fields exist that could store unsanitized content exploitable for stored XSS when rendered to other users

You are affected if your AEM installation version is 6.5.x before 6.5.25.0, 2026.x before 2026.5.0, or exactly 6.5 without the corresponding service pack applied.

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

Upgrade to the latest AEM version or apply the vendor-provided patch. Implement output encoding and input validation on affected form fields as an additional defense layer.

Recommended fix High confidence

AEM 6.5.25.0 or later for 6.5.x LTS line; AEM 2026.5.0 or later for 2026.x release line

  1. 1. Back up the current AEM instance, including repository content, configuration, and custom code.
  2. 2. Review Adobe Experience Manager upgrade documentation for your current version to ensure compatibility with the target version.
  3. 3. Download Adobe Experience Manager 6.5.25.0 (or later 6.5.x LTS release) or 2026.5.0 (or later) from the Adobe distribution portal.
  4. 4. Stop the running AEM instance.
  5. 5. Install the new AEM version using the appropriate method (JAR file installation or upgrade package).
  6. 6. After installation, verify all custom bundles, workflows, and integrations function correctly.
  7. 7. Test the specific form fields that were vulnerable to ensure the XSS vulnerability is remediated.
  8. 8. Restart the AEM instance and verify normal operations.
Caveat AEM major version upgrades may require code adjustments and compatibility testing; custom bundles and integrations should be verified against the new version

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