CVE-2025-47047
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 XSS vulnerability where low-privileged users can inject malicious JavaScript into form fields. When other users view pages containing these compromised fields, the injected scripts execute in their browsers, 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.
-
Identify your Adobe Experience Manager versionAccess the AEM System Information console or check the product version through the AEM home page (typically at /libs/granite/core/content/login.html or via the Help menu > System Information). Compare the version number against the safe thresholds: 6.5.23.0 or later for the 6.5.x line, or 2025.5.0 or later for the cloud-inspired release line.Affected if Your installed version is earlier than 6.5.23.0 (for 6.5.x releases) or earlier than 2025.5.0 (for 2025 releases).
-
Audit existing form submissions for injected scriptsQuery your content repository (via CRXDE Lite or the Query Builder API) for form submission nodes under /content and examine stored values for common XSS patterns such as <script>, javascript:, onload=, onerror=, or other HTML event handlers.Affected if Existing form submission data contains suspicious payloads resembling XSS vectors in any field that is rendered back to users.
You are affected if your AEM version is earlier than 6.5.23.0 or 2025.5.0 AND your environment contains form fields that accept user input and display stored values without 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 per Adobe's official security bulletin. Additionally, audit existing form submissions for malicious payloads and implement output encoding on all user-supplied content displayed in the application.
AEM 6.5.23.0 (for 6.5.x line) or AEM 2025.5.0 (for 2025.x line)
- Identify your current Adobe Experience Manager version by checking the AEM Welcome page or system console
- If running AEM 6.5.x line: Upgrade to AEM 6.5.23.0 or later by applying the latest service pack from Adobe Software Distribution
- If running AEM 2025.x line: Upgrade to AEM 2025.5.0 or later
- After upgrade, verify the form components where the XSS was reported are functioning correctly
- Clear browser cache and test that the stored XSS payload is no longer executable in the affected form fields
- Ensure low-privileged users cannot inject scripts into form fields by creating a test user with limited permissions and attempting to inject a benign script payload
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-47047 — 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-47047 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