CVE-2025-47062
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged authenticated attackers to inject malicious JavaScript into form fields. The malicious payload persists in the application and executes in victim users' browsers when they view pages containing the compromised form 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 the installed Adobe Experience Manager versionAccess the AEM Welcome page and navigate to Tools > Operations > Diagnosis, or check the version via the system console at /system/console/systeminfo. The version is displayed on the Welcome page footer or in the Product Information section.Affected if The installed version is 6.5.22 or earlier, or any version below 2025.5.0.
-
Verify AEM Forms add-on is installed and enabledNavigate to /libs/granite/core/content/login or check the AEM Package Manager at /crx/packmgr. Look for AEM Forms packages or check if Forms functionality appears in the navigation rail.Affected if AEM Forms is installed and form creation/editing capabilities are available to authenticated users.
-
Confirm low-privileged user access to form authoringCheck user group memberships and permissions in the AEM User Administration console at /security/users.html or /security/groups.html. Look for non-admin users assigned to 'forms-user' or 'content-author' groups.Affected if Low-privileged authenticated users have access to create or edit Adaptive Forms or Foundation Form components.
-
Inspect form field configurations for input validationNavigate to the Forms workflow or form container component in AEM authoring mode. Open the form container properties dialog and inspect the Validation settings under the Advanced or Submission tabs.Affected if Form fields lack strict input validation rules or output encoding is not enforced.
The environment is affected if the installed AEM version is below 6.5.23.0 or below 2025.5.0 AND forms with user-editable fields are accessible to low-privileged authenticated 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
Upgrade Adobe Experience Manager to version 6.5.23 or later to obtain the security patch. Additionally, implement input validation and output encoding for all form fields as a defense-in-depth measure.
AEM 6.5.23.0 or later, or AEM 2025.5.0 or later
- 1. Back up the current Adobe Experience Manager instance including content and configurations
- 2. Review the Adobe Experience Manager 6.5.23.0 or 2025.5.0 release notes for any migration requirements
- 3. Upgrade Adobe Experience Manager to version 6.5.23.0 or later, OR upgrade to 2025.5.0 or later depending on your release track
- 4. After upgrade, verify the XSS vulnerability is resolved by testing the previously affected form fields
- 5. Validate that custom components and integrations function correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47062 — 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-47062 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