CVE-2025-46947
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.22 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.
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager form fields affecting versions 6.5.22 and earlier. A low-privileged attacker can inject malicious JavaScript into vulnerable form fields that persists and executes in victim users' browsers when they navigate to pages containing those compromised fields.
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.23.0< 2025.5.0CVSS 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.
-
Check installed AEM versionAccess the AEM Web Console (typically at /system/console/bundles or /crx/packmgr) or check the version file in the installation directory. Navigate to 'Help' > 'About Adobe Experience Manager' in the AEM interface to view the exact version number.Affected if The version shown is below 6.5.23.0 for the 6.5.x release line, or below 2025.5.0 for the 2025 release line.
-
Identify custom form componentsReview the /apps folder in CRX/DE (accessible at /crx/de) for any custom form field components under /apps that extend or modify standard AEM form components. Look for components with 'form' or 'field' in their node names.Affected if Custom form components exist that accept user input and may not have proper output encoding configured.
-
Audit Form containers and fieldsOpen AEM Forms (if enabled) and review existing Adaptive Forms or Foundation Forms. Check the form field configurations in the Form Model or Edit dialog for each field type, specifically looking at the 'Name' and 'Value' binding settings.Affected if Form fields are configured with direct user input bindings that could accept and persist unsanitized content.
-
Review Content Services or Core Components usageIf using AEM Core Components Forms (core/wcm/components/form/*), examine the form container and field component configurations in the page edit mode or in the underlying XML/JSON content structure.Affected if Form fields using Core Components are present and accessible to low-privileged users for input.
Your AEM instance is affected if it runs version 6.5.22.x or earlier, or version 2025.4.x or earlier, and has form fields accessible to low-privileged users that accept and display user-submitted content.
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.23.02025.5.0
Upgrade Adobe Experience Manager to version 6.5.23 or later to apply the security patch that addresses this stored XSS vulnerability.
AEM 6.5.23.0 (for 6.5.x line) or AEM 2025.5.0 (for as a Cloud Service)
- Create a full backup of the AEM repository, content, and database before proceeding with any upgrade
- Review Adobe Experience Manager 6.5.23.0 release notes for any configuration or feature changes that may affect your implementation
- Test the upgrade in a non-production environment first to verify compatibility with custom code and third-party integrations
- For AEM 6.5.x deployments: Upgrade to version 6.5.23.0 or later
- For AEM as a Cloud Service deployments: Upgrade to version 2025.5.0 or later
- After upgrading, clear the AEM cache and rebuild any search indexes if required
- Validate that custom form components and user-generated content fields properly encode output to prevent XSS
- Verify the upgrade by testing the vulnerable form fields with script injection attempts to confirm the fix is effective
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46947 — 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-2025-46947 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