CVE-2026-47977
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 · high confidenceAdobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where low-privileged attackers can inject malicious JavaScript into vulnerable form fields. When victims browse to pages containing these compromised fields, the script executes in their browsers, enabling session hijacking, credential theft, or defacement. The scope change indicates the vulnerability can impact components beyond the vulnerable application's trust boundary.
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 your AEM versionAccess the AEM System Information console at /system/console/status or check the crx-quickstart/package.properties file for the productversion propertyAffected if The version is less than 6.5.25.0, less than 2026.5.0, or exactly 6.5.0 (all of these fall within the affected ranges)
-
Confirm Forms or Adaptive Forms feature is enabledNavigate to Tools > Forms or check the Felix console at /system/console/components for forms-related bundles (com.adobe.aemforms.*)Affected if Forms functionality is installed and accessible to users in your AEM instance
-
Identify custom form fields that accept user inputReview form models and adaptive form configurations in /conf or /content directories for fields using text input, textarea, or similar components that store user-submitted dataAffected if Custom or out-of-the-box forms exist that allow low-privileged users to submit content into text-based fields
-
Verify if low-privileged users have form authoring permissionsCheck user/group permissions in Tools > Security > Permissions or via CRX/DE at /home/groups for contributors or content-authors groups assigned to form submission or authoring rolesAffected if Users with contributor, author, or limited admin roles can access and submit form content
You are affected if your installed AEM version is below 6.5.25.0 or below 2026.5.0 (or exactly 6.5) AND you have forms enabled that allow low-privileged users to input content into form fields, as the stored XSS requires both a vulnerable version and form fields accessible to low-privileged users.
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
Upgrade Adobe Experience Manager to the latest patched version or apply the relevant security hotfix. Additionally, implement output encoding and content security policy headers as defense-in-depth measures.
AEM 6.5.25.0 or later; AEM 2026.5.0 or later
- Verify current Adobe Experience Manager version by checking the AEM welcome page or using the version manifest
- Backup the entire AEM repository (crx-quickstart) and any custom configurations before upgrading
- Review Adobe's upgrade documentation for your specific version path at helpx.adobe.com
- Download Adobe Experience Manager 6.5.25.0 or later (or 2026.5.0/2026.6.0 for the 2026 release line) from the Adobe Software Distribution portal
- Stop the AEM instance gracefully
- Install the upgrade following Adobe's standard upgrade procedure (using the crx-quickstart installer or via package manager)
- After upgrade, verify all custom applications and integrations function correctly
- Test the vulnerable form fields to confirm the XSS fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47977 — 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-47977 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