CVE-2026-47944
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 · uneditedAdobe 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 · moderate confidenceAdobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged attacker can inject malicious JavaScript into vulnerable form input fields, which persists in the system. When other users (typically higher-privileged) browse to pages containing these injected fields, the malicious script executes in their browsers, allowing session hijacking, data theft, or actions on behalf of the victim.
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< 6.5.25.0< 2026.5.0= 6.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Adobe Experience Manager installationCheck for AEM processes or examine web application directories for 'cq' or 'aem' artifacts. Access the AEM welcome page at /libs/granite/core/content/login.html or / to confirm AEM presence.Affected if AEM is confirmed to be running in the environment
-
Determine installed AEM versionNavigate to Help > About Adobe Experience Manager in the AEM console, or access /system/console/configMgr and look for com.day.commons.jcr.embeddedinstaller or check the version.properties file in the crx-quickstart folder.Affected if The version is below 6.5.25.0, below 2026.5.0, or exactly 6.5 (any 6.5.x release)
-
Verify Forms or custom form fields are enabledCheck if AEM Forms module is installed by navigating to /libs/fd/fm/content/console.html, or examine /libs/foundation/components for custom form components, or review the HTML output of published pages for <form> elements accepting user input.Affected if Forms functionality is active and form fields are present on published or authorable pages
-
Check for untrusted user input acceptance in formsReview form component configurations in AEM at /libs/foundation/components/form or custom form containers in /apps. Inspect the form action and whether client-side or server-side input validation is configured.Affected if Forms are configured to accept user-submitted content without proper validation
A user is affected if Adobe Experience Manager is running with a version below 6.5.25.0 (or 6.5.x) or below 2026.5.0, and Forms or custom form fields that accept user input are enabled on the instance.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.5.25.02026.5.0
Update Adobe Experience Manager to the latest patched version as specified in Adobe's security bulletin. Additionally, implement input validation and output encoding on all form fields, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.
AEM 6.5.25.0 (LTS) or AEM as a Cloud Service 2026.5.0 or later
- Verify current AEM version in use by checking the product version in the AEM Web Console or About Adobe Experience Manager page
- Review the AEM 6.5 Service Pack or AEM cloud release notes for version 6.5.25.0 or 2026.5.0 for any specific upgrade instructions
- Backup the current AEM instance including the repository, database, and configuration files
- For AEM 6.5 on-premise: download and install AEM Service Pack 6.5.25.0 from the Adobe Software Distribution portal
- For AEM as a Cloud Service: ensure the environment is updated to the 2026.5.0 release or later through Cloud Manager
- After upgrade, clear the AEM cache and republish any content that may have been stored before the fix
- Verify the fix by testing that the vulnerable form fields no longer execute injected scripts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47944 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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