CVE-2025-47002
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 attackers can inject malicious JavaScript into form fields. When victims browse to pages containing these compromised fields, the malicious scripts execute in their browsers.
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 versionAccess the AEM System Information console or check the version file in the installation directory. The version is typically visible at /system/console or via the 'About Adobe Experience Manager' option in the AEM Welcome screen.Affected if The installed version is lower than 6.5.23.0 or lower than 2025.5.0 (if on the 2025 release track).
-
Verify AEM forms module is enabledCheck the AEM Forms add-on or core components configuration. Navigate to the Forms configuration at /libs/fd/fdm/config or verify that Forms functionality appears in the AEMfelix console at /system/console/components.Affected if The Forms module is installed and active, allowing users to create or edit form fields that could be exploited.
-
Identify accessible form fields for low-privileged usersReview user permissions for groups with limited privileges (such as content-authors or users assigned to custom low-access groups). Check which form components these users can edit in the AEM Sites or Forms authoring environment.Affected if Low-privileged users have write access to form components or form field definitions in AEM.
-
Inspect form field content for suspicious scriptsReview stored form data or form field configurations in the AEM repository under /content/forms or /content/dam/forms. Look for HTML script tags, javascript: URIs, or event handler attributes (onload, onerror, onClick) in text fields.Affected if Any form fields contain encoded or raw JavaScript code, particularly in fields that low-privileged users can edit.
Your environment is affected if AEM version is below 6.5.23.0 (or below 2025.5.0) AND low-privileged users have access to create or edit form fields that contain injected script content.
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 patched version of Adobe Experience Manager (6.5.23 or later). If immediate patching is not feasible, implement input validation and output encoding on affected form fields as a compensating control.
AEM 6.5.23.0 (6.5.x line) or AEM 2025.5.0 (2025.x line)
- 1. Back up your current AEM instance and content repository
- 2. Review Adobe's official AEM upgrade documentation for your current version
- 3. Test the upgrade in a non-production environment first
- 4. Upgrade Adobe Experience Manager to version 6.5.23.0 (for 6.5.x line) or 2025.5.0 (for 2025.x line)
- 5. Verify the fix by testing that form fields no longer execute injected JavaScript payloads
- 6. Deploy to production after successful validation
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-47002 — 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-47002 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