CVE-2025-47044
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 · moderate confidenceAdobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged attacker can inject malicious JavaScript payloads into vulnerable form input fields, which are stored in the system. When other users view pages containing these compromised form fields, the malicious scripts execute in their browsers, potentially allowing session hijacking or unauthorized actions.
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 versionAccess the AEM Web Console (typically at /system/console/configMgr) or check the product.info in the AEM Welcome page. You can also query the bundle version via the OSGi console at /system/console/bundles or use the version.txt file in the crx-quickstart folder.Affected if The installed version is earlier than 6.5.23.0 for the 6.5.x line, or earlier than 2025.5.0 for the cloud release line.
-
Determine if low-privileged user access to form fields is enabledReview the user permissions in AEM Groups (accessible via /libs/granite/security/content/group.html) and check if unauthenticated or low-privileged users have access to form components in the content tree.Affected if Low-privileged users (such as content-authors without admin rights) can access and submit to form components in the AEM content pages.
-
Locate form components accepting user inputSearch the AEM content repository (using CRXDE Lite at /crx/de or the Query tool) for form field components like form-text, form-textarea, or granite/ui/components/coral/foundation/form/textfield that are present in published content pages.Affected if Form components that accept and store user input are present in the AEM content and are publicly accessible or accessible to low-privileged users.
-
Inspect form field configuration for output encodingUsing CRXDE Lite, examine the JSP or HTL scripts for the form components in use. Look for the data-sly-html, escapeXss, or similar encoding mechanisms applied to form field output in the corresponding component scripts under /apps or /libs.Affected if The form component scripts do not implement proper output encoding (such as HTL context-aware escaping or server-side XSS protection) when rendering stored form data.
A user is affected if their AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privileged users can access form fields that lack proper output encoding for stored data.
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 to a version newer than 6.5.22 when available. Until then, implement output encoding for all form field outputs and validate/sanitize user inputs according to AEM's security guidelines.
6.5.23.0 (for 6.x line) or 2025.5.0 (for newer release line)
- Backup your current AEM instance and verify all content is properly backed up
- Download Adobe Experience Manager version 6.5.23.0 (for 6.x line) or 2025.5.0 (for the newer release line) from the official Adobe distribution portal (helpx.adobe.com)
- Stop the AEM instance and ensure all processes are terminated
- Install the upgraded version following Adobe's standard upgrade documentation for your specific deployment
- After installation, verify the XSS vulnerability is remediated by testing that malicious script inputs in form fields are properly sanitized and not executed
- Restart the AEM instance and perform standard smoke tests to ensure core functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47044 — 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-47044 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