CVE-2025-47040
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 confidenceAdobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged attacker can inject malicious JavaScript payloads into vulnerable form input fields, which persist in the system and execute when other users view pages containing the affected 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.
-
Determine AEM versionAccess the AEM System Information console at /system/console/systeminfo or check the version.properties file in the crx-quickstart folder. Look for the 'Adobe Experience Manager' version entry.Affected if The installed version is 6.5.22 or earlier, or falls below 2025.5.0 (for the 2025 release track).
-
Identify form components in useReview your AEM instance for pages and components that use core form components (form, textfield, textarea, numberfield, datepicker, checkbox, radio, dropdown, fileupload) or custom form implementations. Check the CRXDE Lite at /crx/de or use the Query Builder to search for form-related content nodes under /content.Affected if Form components or custom form fields are present in your content structure and accessible to low-privileged users.
-
Verify low-privilege user access to formsReview group and permission configurations in AEM under /useradmin. Identify users or groups with Contributor, Editor, or custom content-author roles. Check if these users can access and edit pages containing form components.Affected if Users with low-privilege accounts (non-admin) have access to create or edit content that contains form input fields.
-
Audit form field configurationsInspect the form component dialogs (XML .xml files under /apps or /libs) for the specific form fields in use. Look for whether these fields accept rich text, HTML, or freeform text input without strict input validation constraints configured.Affected if Form fields are configured to accept unvalidated or rich text input that could persist malicious scripts.
Your environment is affected if you are running Adobe Experience Manager version 6.5.22 or earlier (or pre-2025.5.0) AND your instance exposes form fields that low-privileged users can populate with 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 a version newer than 6.5.22, or apply the relevant security patch. Implement input validation and output encoding on all form fields as a defense-in-depth measure.
AEM 6.5.23.0 (for 6.5.x branch) or AEM 2025.5.0 (for cloud/2025 branch)
- Back up the current Adobe Experience Manager instance and database before proceeding with any upgrade
- Review the official Adobe Experience Manager upgrade documentation for your current version at helpx.adobe.com
- For AEM 6.5.x users: Upgrade to version 6.5.23.0 or later
- For AEM cloud/2025 users: Upgrade to version 2025.5.0 or later
- After upgrading, clear the AEM repository cache and publish the changes
- Verify the upgrade was successful by checking the AEM version in the About Adobe Experience Manager console
- Test that the stored XSS vulnerability is remediated by attempting to inject script content into form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47040 — 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-47040 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