CVE-2025-47017
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 vulnerability where low-privileged users can inject malicious JavaScript into form fields. The injected script persists in the system and executes when other users view the affected pages.
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 System Information console (usually at /system/console/status-productinfo or /crx/packmgr/service.jsp) or check the manifest file in the installation directory. Compare the version number against the affected ranges: versions below 6.5.23.0 or below 2025.5.0 are vulnerable.Affected if The installed version is less than 6.5.23.0 or less than 2025.5.0
-
Identify low-privilege user access to form authoringReview user group permissions in AEM Users or Groups console (accessible at /security/users.html or /security/groups.html). Determine if users with limited permissions (contributor, author, or custom low-privilege groups) have access to create or edit form content, Experience Fragments, or Adaptive Forms.Affected if Low-privilege users (non-admin) have permissions to create or edit form fields or content that is viewable by other users
-
Inspect stored form content for suspicious scriptsUse AEM Query Builder (at /bin/querybuilder.json) or CRX/DE Lite (at /crx/de) to search for content nodes under /content, /etc, or form-related paths. Look for patterns like <script>, javascript:, onload=, onerror=, or encoded variants in text fields. Example query: type=nt:unstructured and path=/content and 0_property=jcr:content/*text* properties.Affected if Form fields, content nodes, or metadata contain unsanitized script tags or event handlers (script, javascript:, on* attributes) that could execute when viewed
-
Review audit and error logs for XSS attemptsAccess AEM error log (usually at /logs/error.log via Felix console at /system/console/slinglog or stored in crx-quickstart/logs). Search for suspicious patterns in form submission parameters, especially from low-privilege user sessions.Affected if Logs show form submissions containing script tags, encoded XSS payloads, or unusual field content from low-privilege accounts
A user is affected if their AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privileged users have access to form authoring capabilities, or if malicious script content is already present in the system.
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 the official Adobe patch when available, implement input validation and output encoding on vulnerable form fields, and consider Content Security Policy headers as defense-in-depth. Existing malicious content should also be cleaned from the system.
6.5.23.0 (for 6.5.x on-premises) or 2025.5.0 (for AEM Cloud Service/2024.x)
- Identify current Adobe Experience Manager version in use (check /system/console/bundles or AEM version info)
- Determine which release line you're on: 6.5.x on-premises or AEM Cloud Service/2024.x
- For 6.5.x on-premises: Upgrade to version 6.5.23.0 or later
- For AEM Cloud Service: Upgrade to version 2025.5.0 or later
- Test the upgrade in a non-production environment first
- Back up the current AEM environment before upgrading
- Apply the upgrade following Adobe's official upgrade documentation
- Verify the fix by confirming the AEM version post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47017 — 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-47017 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