CVE-2025-47071
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 input fields, which persist on the page. When other users subsequently browse to pages containing these compromised fields, the attacker's JavaScript executes in their browsers, potentially allowing session hijacking, credential theft, or defacement.
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.
-
Identify installed AEM versionAccess the AEM System Information console at /system/console/systeminfo or check the version.properties file in the crx-quickstart directory. Also check the About Adobe Experience Manager page (Help > About).Affected if The version is 6.5.22 or earlier, or any version before 2025.5.0 (including 6.5.x releases below 6.5.23.0)
-
Verify AEM 2024.x release versionIf running AEM as a Cloud Service or 2024.x releases, check the exact release version through the same System Information console. AEM releases follow a year.month pattern.Affected if The version is any 2024.x or early 2025.x release below the 2025.5.0 patch
-
Confirm low-privileged user access to FormsCheck if low-privileged users (with Contributor, Editor, or limited Author permissions) have access to create or edit Adaptive Forms, Core Components Form fields, or Foundation Form components. Review group permissions in /useradmin or the Users console.Affected if Low-privileged users can create or modify form components without admin oversight
-
Inspect form component configurationsReview form field components in the CRX/DE repository (accessible at /crx/de) under /apps or /content, looking for Adaptive Form Field components or Core Components Form Field (core/fb) configurations. Check if these components accept user input without server-side validation constraints.Affected if Form field components allow unrestricted text input and store values without sanitization
-
Search for existing XSS payloads in form dataQuery the repository under /content for stored form submission data. Use CRXDE or the Query Builder to search for common XSS patterns like '<script', 'javascript:', 'onerror=', 'onload=' in form field values stored under /content/forms/...Affected if Any form submission data contains unsanitized HTML or JavaScript event attributes
Your environment is affected if you run AEM 6.5.22 or earlier, or any version below 2025.5.0, AND low-privileged users can create or edit form fields where malicious scripts could be stored and served to other 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.23.02025.5.0
Apply Adobe's official patch by upgrading to AEM 6.5.23 or later. Until then, restrict low-privileged user permissions to form creation/editing and implement Content Security Policy headers to mitigate XSS execution.
Adobe Experience Manager 6.5.23.0 or 2025.5.0
- 1. Review the Adobe Experience Manager release notes for versions 6.5.23.0 and 2025.5.0 to understand changes and deprecations
- 2. Create a full backup of your AEM instance, including the repository, database, and configuration files
- 3. Test the upgrade in a staging environment before applying to production
- 4. Upgrade Adobe Experience Manager to version 6.5.23.0 (for 6.x line users) or 2025.5.0 (for newer releases)
- 5. Verify the upgrade was successful by logging into AEM and checking the version in the About Adobe Experience Manager dialog
- 6. Test the specific form fields that were vulnerable to confirm the XSS vulnerability is remediated
- 7. Deploy the upgraded instance to production
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-2025-47071 — 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-47071 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