CVE-2025-47001
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-privileged attacker can inject malicious JavaScript payloads into vulnerable form inputs, which are then persisted and executed in the browsers of users who view the affected pages.
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.22.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 page at /system/console/status-productinfo or check the version.properties file in the crx-quickstart folder. Compare the displayed version against 6.5.22.0 and 2025.5.0.Affected if The installed version is below 6.5.22.0 for the 6.5.x line, or below 2025.5.0 for the cloud-era release line.
-
Locate custom form componentsIn the AEM Assets console, search for form-related content fragments or custom form components under /apps or /content that accept user input. Check the form builder or experience fragment usages.Affected if Custom or out-of-the-box form components that accept text input are present in the content structure.
-
Inspect form field configurationsOpen the form component dialogs in edit mode for any identified forms. Review the field type settings and check whether the "Use HTML5 type attribute" or similar input type constraints are configured.Affected if Form fields are configured with minimal input type constraints or allow raw text entry without specific type enforcement.
-
Audit form submission endpointsReview the form action configuration in AEM Forms or the submit action assigned to each form component. Identify which submit handler processes the form data.Affected if Forms point to custom submit handlers or store data in repositories without server-side input validation configured.
-
Scan content repository for injected scriptsUse the AEM Query Builder or CRX/DE Lite to search repository nodes under /content for common XSS payloads or script tags in form-related fields. Run a query for nodes containing '<script' or 'javascript:' patterns.Affected if Any stored content nodes contain unsanitized script tags or event handler attributes within form-related fields.
The environment is affected if the installed AEM version is below the patched releases and forms accepting user input are in use without additional input validation controls.
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.22.02025.5.0
Upgrade Adobe Experience Manager to version 6.5.23 or later to obtain the vendor patch. Alternatively, implement output encoding and input validation on affected form fields, and enforce Content Security Policy headers to mitigate XSS execution.
Adobe Experience Manager 6.5.22.0 or later, or 2025.5.0 or later
- Review the Adobe Experience Manager upgrade documentation at helpx.adobe.com for detailed upgrade procedures
- Ensure your current system meets the prerequisites for upgrading to version 6.5.22.0 or later
- Create a full backup of your AEM instance including the repository, database, and configurations
- Test the upgrade in a non-production environment before deploying to production
- Upgrade Adobe Experience Manager to version 6.5.22.0 or later (for 6.5.x line) OR to version 2025.5.0 or later (for the newer release line)
- Verify that the upgrade was successful and all custom configurations are intact
- Test the specific form fields that were vulnerable to ensure the XSS vulnerability is remediated
- Deploy the upgraded version to production after successful testing
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-47001 — 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-47001 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