CVE-2026-47958
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager forms allows low-privileged attackers to inject malicious JavaScript into form fields. When victims browse to pages containing the compromised fields, the injected script executes in their browsers. The scope change indicates impact extends beyond the vulnerable component itself.
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 installed AEM versionAccess AEM system information via the Web Console (navigate to /system/console/status-productinfo) or check the version file in the crx-quickstart folder. Compare the version number against the affected ranges: < 6.5.25.0, < 2026.5.0, or exactly 6.5.Affected if The installed AEM version is below 6.5.25.0, below 2026.5.0, or reports as version 6.5 exactly
-
Verify low-privilege user access to formsReview AEM user group permissions in the Groups console ( Security > Groups ) and check form component configurations in the Touch UI ( Tools > General > Form Builder ) or Classic UI to confirm whether users with low-level permissions (such as contributors or content authors with limited rights) can access and edit form fields.Affected if Authenticated users with low-level permissions (non-admin) have write or edit access to any form field components
-
Inspect form content for suspicious scriptsSearch the AEM content repository using CRXDE Lite ( /crx/de ) or Query Builder to examine stored form field values. Look for form field nodes containing script tags, javascript: prefixes, or HTML event handlers (onclick, onerror, onload, etc.) within the content structure.Affected if Any stored form field values contain unencoded script tags, javascript: URIs, or HTML event handler attributes that would execute when rendered
The environment is vulnerable if the installed AEM version falls within the affected range AND low-privilege authenticated users can inject content into form fields that gets stored and displayed without output encoding.
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 vendor patches for AEM versions 6.5.24, LTS SP1, and 2026.04 or later. Implement input validation/sanitization on form fields and consider Content Security Policy headers as additional defense.
Upgrade to Adobe Experience Manager 6.5.25.0 (for 6.5.x LTS line) or 2026.5.0 (for the 2026.x release line)
- Backup your current Adobe Experience Manager instance and verify all custom configurations
- Review the Adobe Experience Manager 6.5 Service Pack release notes and 2026.x release notes for the specific fixes included in 6.5.25.0 and 2026.5.0
- Test the upgrade in a non-production environment before deploying to production
- Download the appropriate Service Pack or release from the Adobe Distribution Package Builder or Software Distribution portal
- Install the Service Pack via the AEM Service Pack installer or using the command line (e.g., java -jar aem-service-pkg-6.5.25.0.jar), or deploy the 2026.5.0 release
- Verify the installation completed successfully by checking the /system/console/status about the AEM version
- Clear the AEM cache and republished content to ensure no cached malicious scripts remain
- Test the specific form fields that were vulnerable to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47958 — 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-47958 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