dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-47943

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 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged attacker can inject malicious JavaScript payloads into vulnerable form input fields, which persist on the page and execute when other users browse to the affected content. The scope change indicates the vulnerability impacts components beyond the initial injection point.

MitigationApply the vendor patch for CVE-2026-47943 to upgrade to a fixed AEM version. Until patched, implement output encoding and input validation on all form field submissions and display contexts.

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. Check installed AEM version
    Navigate to AEM Welcome page > Tools > Operations > Diagnosis, or access /system/console/configMgr and locate the version information. Alternatively, check the version.properties file in the crx-quickstart folder.
    Affected if The installed version is 6.5 (any build) or below 6.5.25.0, or below 2026.5.0.
  2. Identify Forms usage in the environment
    Review the AEM instance for any Forms components, Adaptive Forms, or custom form implementations. Check content pages under /content for form-based workflows, comment sections, or user-submitted content areas.
    Affected if Form fields that accept user input exist and can be accessed by low-privileged users.
  3. Audit custom form components for output encoding
    Review any custom Form or Adaptive Form components under /apps or /libs. Inspect the JSP, HTL, or Sightly templates for usage of encoding functions such as XSSAPI or ESAPI encoding utilities when rendering form field values.
    Affected if Custom form components do not use proper output encoding (XSSAPI, org.apache.sling.xss.XSSAPI, or equivalent) when rendering user-supplied values.
  4. Check server-side input validation configuration
    Examine the XSS Protection configuration in AEM at /system/console/configMgr for the XSSAPI and any custom input validation filters. Review form submission handlers for server-side validation presence.
    Affected if Server-side input validation and sanitization are disabled or missing on form submission endpoints.

Your environment is affected if the installed AEM version falls within the affected range (6.5 or < 6.5.25.0 or < 2026.5.0) AND form fields accepting user input are present without proper output encoding or server-side validation.

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

Apply the vendor patch for CVE-2026-47943 to upgrade to a fixed AEM version. Until patched, implement output encoding and input validation on all form field submissions and display contexts.

Recommended fix High confidence

6.5.25.0 (for 6.5 LTS branch) or 2026.5.0 (for 2026 release branch)

  1. 1. Identify the current Adobe Experience Manager version in use (e.g., 6.5.24, LTS SP1, or 2026.04 and earlier)
  2. 2. If running 6.5.x LTS branch: upgrade to version 6.5.25.0 or later
  3. 3. If running 2026.x release branch: upgrade to version 2026.5.0 or later
  4. 4. After upgrading, clear any cached content and rebuild the project to ensure all components are updated
  5. 5. Verify the fix by testing that previously vulnerable form fields no longer execute injected JavaScript code

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