CVE-2026-47941
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager allows low-privileged users to inject malicious JavaScript into form fields. When other users view pages containing these compromised fields, the injected script executes in their browsers, potentially enabling session hijacking or data theft.
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.
-
Determine AEM product versionAccess the AEM welcome page and navigate to Help > About Adobe Experience Manager, or append /system/console/product.json to your AEM instance URL to retrieve the version information.Affected if The displayed version is 6.5.24 or earlier, 2026.04 or earlier, or falls within the 6.5.x LTS release line before 6.5.25.0.
-
Verify AEM 2026 release versionIf the version begins with 2026, check the specific release by accessing /system/console/product.json or the About page. Compare the minor version number.Affected if The version is 2026.04 or any 2026 release prior to 2026.5.0.
-
Identify form field usage in AEMReview AEM sites, templates, or custom components that contain form input fields such as text fields, textareas, or other user-editable form elements. Use CRXDE Lite (accessible at /crx/de) to search for form-related components under /apps or /libs.Affected if Form fields exist that accept user input and are rendered on published pages without additional server-side validation.
-
Check for low-privileged user access to formsReview AEM user and group permissions to determine if low-privileged users (such as those with contributor or author-level access) can create or edit content containing form fields.Affected if Low-privileged users have the ability to create or modify form-based content in AEM.
Your environment is affected if the installed AEM version matches the affected ranges (6.5.24 or earlier, 6.5 LTS before 6.5.25.0, or 2026.04 or earlier) AND your AEM deployment exposes form fields that accept user input accessible to low-privileged authors.
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
Apply the vendor patch for CVE-2026-47941 when available. Until then, implement strict input validation on all form fields and ensure proper output encoding when rendering user-supplied content.
Adobe Experience Manager 6.5.25.0 (LTS) or 2026.5.0+ (2026 release)
- Identify the current Adobe Experience Manager version in use (check /system/console/configMgr or About Adobe Experience Manager)
- Schedule a maintenance window for the upgrade
- Back up the AEM instance completely including the repository, database, and configurations
- For AEM 6.5 LTS line: Upgrade to version 6.5.25.0 or later
- For AEM 2026 release line: Upgrade to version 2026.5.0 or later
- Test the upgrade in a staging environment before applying to production
- Apply the upgrade following Adobe's official documentation (helpx.adobe.com)
- After upgrade, verify the XSS vulnerability is resolved by testing the affected form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47941 — 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-47941 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