CVE-2025-47034
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 where low-privileged attackers can inject malicious JavaScript into form fields. The malicious payload persists in the system and executes when users view pages containing the affected 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 Adobe Experience Manager installation and versionLocate the AEM installation and check the version number. This is typically visible in the AEM About dialog (Help > About Adobe Experience Manager) or in the crx-quickstart folder via the version.properties file.Affected if The installed version is lower than 6.5.23.0 or lower than 2025.5.0
-
Confirm AEM product line branchDetermine whether the installation is the 6.5.x on-premise branch or the newer 2025.x release train. The version format indicates the branch: 6.5.x versions follow the 6.5.x pattern while 2025.x versions follow the year.month pattern.Affected if The version falls into either of the two affected ranges and matches the CVE scope
-
Determine if form fields accepting user input existReview the AEM instance for any Form components, Adaptive Forms, or custom form implementations that accept user input. Check Content Fragments, Experience Fragments, or any user-created content components that include input-capable fields.Affected if The AEM instance contains form components or input fields that store and display user-submitted data to other users
-
Check for presence of low-privileged user accountsReview the user permissions in AEM to identify accounts with limited privileges that have access to create or edit content containing form fields. Check user groups and their content modification capabilities.Affected if Low-privileged users have write access to any form fields or content areas where malicious scripts could be injected
-
Inspect stored form data for suspicious contentExamine the repository (CRX/Content Repository) for existing form submissions or user-generated content that may contain script tags, javascript: URIs, or event handler attributes in form field values.Affected if Any stored form data contains unsanitized HTML or JavaScript code that could execute when rendered
The environment is affected if the installed AEM version is below 6.5.23.0 or below 2025.5.0 AND the system contains form fields that accept and display user input to other users.
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
Implement input validation and output encoding on all form fields that accept user input, and upgrade to AEM version 6.5.23 or later which contains the official patch.
6.5.23.0 (for 6.5.x LTS) or 2025.5.0 (for 2025.x release track)
- 1. Identify your current Adobe Experience Manager version in the AEM About console (Help > About Adobe Experience Manager)
- 2. Determine which release track you are on (6.5.x LTS or 2025.x cloud release)
- 3. If on 6.5.x LTS track: Plan upgrade to version 6.5.23.0 or later
- 4. If on 2025.x track: Plan upgrade to version 2025.5.0 or later
- 5. Review Adobe's release notes for the target version to understand changes
- 6. Test the upgrade in a non-production environment before deploying to production
- 7. Perform a full backup of your AEM instance before upgrading
- 8. Apply the upgrade following Adobe's standard upgrade documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47034 — 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-47034 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