CVE-2025-47051
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 that persists in the system and executes when other users browse to 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 installed AEM versionAccess the AEM Welcome page and navigate to Help > About Adobe Experience Manager, or access /system/console/configMgr and check the com.adobe.granite.packaging.internal.AemVersionGetter bundle info. Compare the version number against the affected ranges: < 6.5.23.0 or < 2025.5.0.Affected if The installed version is 6.5.22 or earlier, or falls below 2025.5.0.
-
Identify form field usage in AEMNavigate to the Sites console and examine pages that contain form components. Check for Adaptive Forms, Core Components form fields (core/wcm/components/form/*), or custom form implementations under /apps. Look for components that accept and store user input.Affected if Form components that accept and store user input are present in the AEM instance.
-
Check for unvalidated form field storageReview the form component configuration under /libs or /apps. Examine the edit dialog configurations (cq:dialog) for form fields to determine if input validation or output encoding is implemented. Inspect the HTL/Sightly templates rendering the form output for proper encoding.Affected if Form fields lack input validation or output encoding in their component configuration or rendering templates.
-
Verify low-privilege user access to formsUsing CRX/DE Lite (accessible at /crx/de), check if standard users or members of the 'authors' group have write access to form field content nodes under /content or /apps. Low-privilege users must be able to contribute form content for the XSS to be exploitable.Affected if Low-privilege users can create or modify content in form fields without elevated permissions.
A user is affected if their AEM version is below 6.5.23.0 or 2025.5.0 AND the system has form components that accept user input without proper validation or encoding, AND low-privilege users can submit form 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
Update Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement input validation and output encoding for form fields as a defense-in-depth measure.
Adobe Experience Manager 6.5.23.0 or AEM as a Cloud Service 2025.5.0
- Identify your current Adobe Experience Manager deployment type (AEM 6.5.x on-premise or AEM as a Cloud Service)
- For AEM 6.5.x on-premise: Upgrade to version 6.5.23.0 or later by obtaining the updated package from Adobe
- For AEM as a Cloud Service: Ensure your environment is updated to version 2025.5.0 or later through the Cloud Manager
- After upgrading, verify that the stored XSS vulnerability is remediated by testing that malicious scripts in form fields are properly sanitized
- Confirm that existing forms and workflows function correctly after the upgrade
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-47051 — 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-47051 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