CVE-2025-47016
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-privilege attacker can inject malicious JavaScript payloads into vulnerable input fields, which are then stored and executed in the browsers of users who 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.
-
Determine AEM versionAccess the AEM System Information page at /system/console/status-productinfo or check the footer of the AEM welcome page. Compare the displayed version against the affected ranges: below 6.5.23.0 or below 2025.5.0.Affected if The installed version is 6.5.22.x or earlier, or falls below 2025.5.0 for the 2025 release line.
-
Identify custom form componentsNavigate to the CRXDE Lite at /crx/de and search for custom form components under /apps that extend the foundation form components. Inspect the JSP or HTL templates for form input fields.Affected if Custom form components exist that may lack proper output encoding on form field labels or values.
-
Review form field output encodingIn CRXDE Lite, examine the JSP or HTL files for form components in /libs/foundation/components/form and any custom equivalents. Look for whether HTL attributes use context-aware encoding (e.g., ${properties.title @ context='html'}) or if raw values are rendered.Affected if Form field templates render user-submitted values without proper context-aware encoding, allowing script injection.
-
Audit stored form data for suspicious contentUse the Query Builder API or access the CRX repository directly to query form submission nodes (typically under /content/forms/af) for patterns matching script tags, javascript:, or event handlers like onload/onerror.Affected if Form submission data contains unsanitized script tags or JavaScript event handlers that could execute in user browsers.
-
Check for low-privilege user access to formsIn the AEM User Administration console at /security/users.html or /libs/cq/security/content/admin.html, verify which users or groups have access to create or edit form content. Identify if low-privilege users (contributors, content authors) can submit forms.Affected if Low-privilege users have access to submit forms that render on pages viewed by other users, enabling stored XSS execution.
Your environment is affected if running AEM below version 6.5.23.0 or below 2025.5.0 AND your forms render user-supplied input without proper output encoding.
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 vendor patch for AEM 6.5.22 or later. Additionally, implement input validation and output encoding on form fields to prevent XSS, and consider Content Security Policy headers.
6.5.23.0 or later; 2025.5.0 or later
- 1. Identify the current Adobe Experience Manager version in use (check About Adobe Experience Manager in the product)
- 2. If running the 6.5.x version line, upgrade to version 6.5.23.0 or later
- 3. If running a 2024.x or earlier version of the newer release line, upgrade to version 2025.5.0 or later
- 4. After upgrading, clear the AEM dispatcher cache and republish any affected content
- 5. Verify the fix by confirming the upgraded version number and testing that form fields properly sanitize input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47016 — 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-47016 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