CVE-2025-47114
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged authenticated users to inject malicious JavaScript payloads into form fields. The injected script persists in the system and executes in the browsers of users who view pages containing the compromised fields.
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 the installed AEM versionNavigate to the AEM Welcome page and click 'Version' under 'Operations', or access /system/console/systeminfo to view the Product Information section showing the full version numberAffected if The displayed version is lower than 6.5.23.0 or lower than 2025.5.0 (for cloud/2024 releases)
-
Locate form field configurationsAccess the AEM Forms interface at /aem/forms and review form models or adaptive form configurations stored under /conf or /contentAffected if Form fields exist that accept user input and do not have explicit output encoding or XSS protection configured
-
Inspect form data for unsanitized contentUse CRX/DE (developer tools) at /crx/de to navigate to form submission nodes under /content/forms/submit or the relevant data store, and inspect stored values for unescaped HTML or script tagsAffected if Form submission data contains raw script tags, javascript: URIs, or unencoded HTML elements that would execute if rendered
-
Check Content Security Policy headersReview dispatcher configuration files (dispatcher.any or .conf) and AEM HTML Library Manager settings at /system/console/configMgr to verify if CSP headers are configured to block inline scriptsAffected if CSP headers are missing or allow 'unsafe-inline' directives, enabling XSS execution
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND your forms accept user input without proper output encoding or CSP restrictions.
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 output encoding on form fields and consider Content Security Policy headers to mitigate XSS execution.
AEM 6.5.23.0 or later; AEM as a Cloud Service 2025.5.0 or later
- Identify your current Adobe Experience Manager version by checking the product console or system information
- Determine which product line you're using: AEM 6.5 (on-premise) or AEM as a Cloud Service
- For AEM 6.5 on-premise: Upgrade to version 6.5.23.0 or later
- For AEM as a Cloud Service: Upgrade to version 2025.5.0 or later
- Review the Adobe Experience Manager release notes for the target version to understand included fixes
- Plan and schedule the upgrade in a non-production environment first
- Test your custom applications and workflows in the staging environment
- After successful testing, schedule a maintenance window for production upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47114 — 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-47114 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