CVE-2025-47092
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. A low-privilege authenticated attacker can inject malicious JavaScript payloads into vulnerable form fields. When other users view pages containing these compromised fields, the malicious script executes in their browsers, potentially enabling 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.
-
Check installed AEM versionAccess the Adobe Experience Manager Felix Console at /system/console/status or check the version.txt file in the crx-quickstart folder. Alternatively, query the JMX MBean 'Adobe Experience Manager' via the OSGi web console at /system/console/jmx.Affected if The installed version is below 6.5.23.0 (for 6.x releases) or below 2025.5.0 (for Cloud Service/2025 releases).
-
Verify the version is in the affected rangeCompare your identified version number against the affected ranges: versions earlier than 6.5.23.0, or versions earlier than 2025.5.0.Affected if Your AEM version matches the affected ranges.
-
Identify custom form components accepting user inputReview the AEM Forms or custom form components in your implementation. Check the component definitions under /apps for form fields that accept user input, particularly those that store data in the repository.Affected if Your environment uses custom or out-of-the-box form components that store user input without proper output encoding.
-
Confirm low-privilege user access to form authoringReview user permissions in AEM under /useradmin. Verify if users with low privileges (contributors, content authors without admin rights) can create or edit form content that gets stored and displayed to other users.Affected if Low-privilege authenticated users can author form content that is subsequently rendered to other users.
-
Audit form field output encodingInspect the HTL templates or JSP/Serlvets handling form data rendering. Check if form fields use proper output encoding functions (such as context-aware encoding in HTL using ${properties.value @ context='html'} or equivalent).Affected if Form fields render user-submitted content without output encoding, allowing script injection.
You are affected if your AEM version is below 6.5.23.0 (6.x) or below 2025.5.0, AND your environment contains form fields that accept user input and render that content to other users 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
Update Adobe Experience Manager to version 6.5.23 or later to obtain the vendor patch. Additionally, implement strict input validation and output encoding on all form fields, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.
AEM 6.5.23.0 (for 6.5.x line) or AEM 2025.5.0 (for 2025.x line)
- 1. Identify current Adobe Experience Manager version in production
- 2. If running AEM 6.5.x: Plan upgrade to version 6.5.23.0 or later
- 3. If running AEM 2025.x: Plan upgrade to version 2025.5.0 or later
- 4. Create full backup of AEM instance and content repository before upgrade
- 5. Test upgrade in non-production environment first
- 6. Apply the upgrade following Adobe's standard upgrade documentation
- 7. Verify the XSS vulnerability is remediated by testing the previously affected form fields
- 8. Deploy to production environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47092 — 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-47092 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