CVE-2025-47073
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 where low-privileged authenticated users can inject malicious JavaScript into form fields. The payload persists in the application and executes in victim browsers when they 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 AEM versionLog in to AEM as an administrator and navigate to the Help menu > About Adobe Experience Manager, or access the system console at /system/console/configMgr and look for the 'Adobe Experience Manager Version' entry. Alternatively, check the version.properties file in the crx-quickstart folder.Affected if The installed version is less than 6.5.23.0 or less than 2025.5.0 (cloud version).
-
Review user group permissionsNavigate to the User Administration console at /useradmin or use the Groups console to identify users assigned to low-privilege groups such as 'content-authors' or 'users'. Verify if these groups have write access to form components or experience fragments.Affected if Low-privileged users have access to create or edit form content without administrative oversight.
-
Inspect form components in useAccess the AEM Assets console and search for form container components (core form or foundation form components) in the content hierarchy. Use CRXDE Lite at /crx/de to navigate to /content and inspect nodes under form containers.Affected if Form components are present and editable by low-privileged users in the content tree.
-
Examine stored form data for malicious scriptsUsing CRXDE Lite, query the repository for form submission data or content nodes containing form fields. Inspect the jcr:content or paragraph nodes for any stored script tags in text fields.Affected if Any form field data contains unsanitized script tags, iframe tags, or event handler attributes (onclick, onerror, etc.).
A user is affected if their AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privileged authenticated users can access and modify form fields where malicious scripts could be stored and later rendered.
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 a version newer than 6.5.22. Additionally, implement robust input validation and output encoding on all form fields, and consider deploying a Content Security Policy (CSP) header to mitigate XSS execution.
6.5.23.0 (for 6.5.x line) or 2025.5.0 (for 2025.x line)
- 1. Identify the current Adobe Experience Manager version in use (check /system/console/bundles or AEM welcome page)
- 2. Determine which release line the installation belongs to (6.5.x legacy line or newer 2025.x cloud line)
- 3. For 6.5.x installations: plan upgrade to version 6.5.23.0 or later
- 4. For 2025.x installations: plan upgrade to version 2025.5.0 or later
- 5. Create a full backup of the AEM repository (crx-quickstart) and database before upgrading
- 6. Test the upgrade in a non-production environment to verify compatibility with custom code and integrations
- 7. Schedule a maintenance window and perform the upgrade following Adobe's official upgrade documentation
- 8. After upgrade, verify the XSS fix is applied by checking that malicious scripts in form fields are properly escaped and not executable
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-47073 — 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-47073 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