CVE-2025-47000
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 payload 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.
-
Identify your Adobe Experience Manager versionAccess the AEM System Information console or check the version.properties file in the installation directory. Compare the installed version against the affected ranges: versions below 6.5.23.0 or versions below 2025.5.0.Affected if The installed version is less than 6.5.23.0 or less than 2025.5.0
-
Determine if low-privilege user accounts existReview user groups and permissions in AEM CRXDE Lite or the User Management console. Identify any users assigned to low-privilege groups such as 'content-authors' or similar read/write roles that can access form components.Affected if Low-privilege users with form editing capabilities exist in the system
-
Audit form components that accept user inputNavigate to the AEM Forms or Experience Fragments sections in the AEM Assets console. Identify form containers, adaptive forms, or content fragments that store user-submitted data in the repository.Affected if Form fields or editable content components are present and accessible to low-privilege users
-
Search for suspicious scripts in form dataUse the AEM Query Builder or CRXDE Lite to search repository nodes under /content or /etc for script tags, javascript: URIs, or event handler attributes (onerror, onload, onclick) stored in text fields.Affected if Malicious script payloads are found stored in form field repository nodes
-
Verify output encoding configurationCheck the Sling Rewriter pipeline configuration or any custom encoder servlet filters that process form field output. Determine if output encoding is applied before content is rendered to users.Affected if Output encoding is not configured or is disabled for form output paths
Your environment is affected if the AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privilege users have access to form fields where malicious scripts could be injected and stored.
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 output encoding and input validation on form fields to prevent XSS execution.
Adobe Experience Manager 6.5.23.0 (for 6.5.x line) or 2025.5.0 (for 2025 line)
- 1. Back up your current AEM instance, including the repository, configuration, and any custom code.
- 2. Review the Adobe Experience Manager 6.5.23.0 (or 2025.5.0 for cloud) release notes for any specific upgrade requirements or breaking changes.
- 3. Download the fixed version from the Adobe Software Distribution portal or through your Adobe EMS/ licensing portal.
- 4. Test the upgrade thoroughly in a non-production/staging environment before deploying to production.
- 5. Execute the upgrade following Adobe's standard upgrade documentation for your deployment model (on-premise, AMS, or Cloud).
- 6. After upgrade, validate that the XSS vulnerability is patched by attempting to inject script content into the affected form fields and confirming it is properly escaped or sanitized.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47000 — 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-47000 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