CVE-2025-47077
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 in form fields. A low-privilege authenticated attacker can inject malicious JavaScript payloads into vulnerable form input fields. When other users subsequently view pages containing these compromised form fields, the embedded malicious script executes in their browsers, potentially allowing session hijacking, data theft, or actions performed on behalf of the victim.
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 installed AEM versionAccess the AEM System Information console at /system/console/configMgr or check the version via the Help menu in the AEM interface. Look for the version number displayed in the 'Adobe Experience Manager' section.Affected if Version is earlier than 6.5.23.0 or earlier than 2025.5.0 (e.g., 6.5.22, 6.5.21, etc.)
-
Locate form components in the AEM instanceNavigate to the Granite UI Form components at /libs/granite/ui/components/coral/foundation/form or review the CRX/DE at /apps for custom form implementations. Check for any form field components that accept user input.Affected if Form components exist that allow unauthenticated or low-privilege user input
-
Verify if forms render user-supplied content without encodingInspect the JSP or HTL scripts for form field components (typically in /apps/*/components/form/*). Look for EL expressions or output that directly render field values without using context-aware encoding functions like ${text field.value} or @ context='html'.Affected if Form field templates use unsafe rendering that does not escape user input
-
Review Content Security Policy headersCheck the Apache Sling dispatcher configuration or the HTTP response headers for existing CSP policies. Use browser DevTools or a curl command: curl -I <aem-url> to inspect response headers.Affected if CSP headers are missing or too permissive, allowing script execution from injected payloads
-
Test for stored XSS in form submissionUsing a low-privilege test account, submit a form with a benign XSS payload such as <script>alert(1)</script> in text input fields. Then view the submitted data or a page rendering that data as another user to observe if the script executes.Affected if The payload executes as JavaScript when the form data is rendered
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND your instance exposes form fields that accept user input and render it 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
Upgrade Adobe Experience Manager to version 6.5.23 or later per Adobe's security bulletin. Implement strict input validation on form fields and ensure proper output encoding when rendering user-supplied content. Consider deploying Content Security Policy headers to mitigate XSS execution.
6.5.23.0 or later (6.5.x line); 2025.5.0 or later (2025.x line)
- Identify the current Adobe Experience Manager version in use (6.5.x or 2025.x release line)
- For 6.5.x line: upgrade to version 6.5.23.0 or later
- For 2025.x line: upgrade to version 2025.5.0 or later
- Test the upgrade in a staging or development environment before deploying to production
- After upgrading, verify that form fields properly sanitize user input to confirm the XSS vulnerability is remediated
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-47077 — 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-47077 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