CVE-2025-47010
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 authenticated attacker can inject malicious JavaScript payloads into vulnerable form input fields. When other users browse to pages containing these compromised fields, the stored scripts execute in their browsers, potentially enabling session hijacking, credential theft, or defacement.
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 System Information console at /system/console/status-productinfo or check the crx-quickstart/license.properties file for the product version stringAffected if The version is below 6.5.23.0 or below 2025.5.0
-
Confirm AEM Forms module is in useNavigate to the AEM Forms interface at /aem/forms or check for form-related bundles in the OSGi console at /system/console/bundlesAffected if Forms functionality is enabled and accessible to users
-
Verify user access controls for form editingReview group permissions in AEM Users or Groups console at /security/users.html or /security/groups.html, checking if low-privileged users (non-admin) have access to create or edit Adaptive Forms or Foundation FormsAffected if Low-privileged authenticated users can access and modify form fields without admin rights
-
Inspect form field configuration for input validationOpen a sample form in edit mode, select a text field, and examine the Properties panel for Validation settings; check if pattern validation or input masks are configuredAffected if Form fields lack input validation rules or pattern constraints
-
Check output encoding settings for form componentsInspect the HTL/Sightly template source for form components in /apps or check the XSS configuration at /system/console/configMgr/org.apache.sling.scripting.sightly.spi.data.DataProvider, looking for context-aware encoding settingsAffected if Output encoding is disabled or not applied to form field rendering
A user is affected if their AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privileged users can access form fields that lack proper input validation and output encoding.
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 which contains the security fix. Additionally, implement output encoding and input validation for all form fields as a defense-in-depth measure.
AEM 6.5.23.0 or later; AEM 2025.5.0 or later
- 1. Review Adobe Experience Manager release notes for version 6.5.23.0 or 2025.5.0 to understand changes and potential compatibility impacts
- 2. Create a backup of the current AEM instance including the repository, database, and configuration files
- 3. Test the upgrade in a staging environment before applying to production
- 4. For AEM 6.5.x: Upgrade the AEM instance to version 6.5.23.0 or later
- 5. For AEM 2025.x: Upgrade the AEM instance to version 2025.5.0 or later
- 6. Verify the upgrade completed successfully by checking the AEM version in the system console (e.g., /system/console/status)
- 7. Test critical workflows and forms to ensure functionality is intact after the upgrade
- 8. Clear AEM caches and rebuild any search indexes if necessary
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47010 — 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-47010 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