CVE-2025-47019
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 (XSS) vulnerability in form fields. A low-privilege attacker can inject malicious JavaScript into these fields, which executes in victim browsers when they view the affected page.
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.
-
Verify AEM version against affected rangesCheck the installed Adobe Experience Manager version in the Help > About Adobe Experience Manager menu, or via the system console (/system/console/systeminfo). Compare the version number to the affected ranges: versions below 6.5.23.0 or versions below 2025.5.0 are vulnerable.Affected if The installed version is 6.5.22.x or earlier, or the version is earlier than 2025.5.0 (for cloud/as-a-service deployments).
-
Identify custom form field componentsReview the AEM Forms or custom form components in the /apps or /content directories. Look for form field components that accept user input and store submissions in the repository, particularly custom xtype or granite:dataSource implementations.Affected if Custom form field components exist that store user input without proper output encoding.
-
Check form submission storage locationsExamine the JCR content repository for form submission nodes under /content/forms/af or custom form paths. Inspect the stored data for any existing injected scripts using a repository query or CRX/DE Lite.Affected if Form submission nodes contain unencoded HTML or script tags in field values.
-
Review Content Services or API endpointsIf AEM Forms or custom APIs expose form data as JSON or XML via endpoints, test whether stored XSS payloads in form fields execute when the data is retrieved and rendered by another user.Affected if Form data is exposed through APIs without server-side output encoding before rendering.
You are affected if your AEM version is below 6.5.23.0 (or below 2025.5.0 for cloud) AND your implementation uses custom form fields that accept and store user-submitted content without 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 to patch the XSS vulnerability. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure.
AEM 6.5.23.0 (for 6.5.x line) or AEM 2025.5.0 (for Cloud Service)
- Identify the current Adobe Experience Manager version in use by checking the product console or system information
- For AEM 6.5.x deployments: Upgrade to AEM 6.5.23.0 or later
- For AEM as a Cloud Service deployments: Upgrade to 2025.5.0 or later
- After upgrade, verify the XSS protection is working by testing form field inputs with script tags
- Ensure that Content Security Policy (CSP) headers are properly configured to provide defense-in-depth against XSS attacks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47019 — 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-47019 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