CVE-2025-47003
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 attacker can inject malicious JavaScript into form inputs, which persists in the system. When legitimate users view pages containing these compromised fields, the injected script executes in their browsers, potentially stealing session cookies or performing actions on behalf of the victim.
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.
-
Determine AEM versionAccess the AEM Welcome page or navigate to /system/console/config and check the version information. Alternatively, check the crx-quickstart/package/version.info file if accessible.Affected if The installed version is lower than 6.5.23.0 or lower than 2025.5.0 (for cloud/2025 releases)
-
Identify AEM Forms usageCheck if AEM Forms addon is installed by navigating to /libs/fd/fm/content/main.html or checking for form-related packages in /crx/packmgr. Look for form models in /content/forms/af/Affected if AEM Forms is enabled and forms with user-submitted data are stored in the system
-
Inspect form field data storageQuery the AEM repository using CRXDE Lite (accessible at /crx/de) or the Query Builder. Search nodes under /content/forms/af/ for form submissions containing script tags or JavaScript event handlers.Affected if Form submission data contains unsanitized HTML tags, script elements, or event handler attributes like onerror, onload, or onclick
-
Review form field input validationExamine the form field component configuration in /libs/fd/af/components/ or custom form models. Check if the allowedParents or allowedChildren policies permit script tags, or review the Granite UI Form field constraints.Affected if Form field components do not implement strict input validation or output encoding for submitted values
-
Check for malicious content in published contentUse the Query Builder to search published pages that render form field data. Look for stored XSS payloads in content nodes under /content/ that get rendered without proper encoding.Affected if Published pages render form field values that contain unescaped HTML or JavaScript code
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND your system stores form submissions that may contain unsanitized user input rendered on pages viewed by 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
Upgrade Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement output encoding and Content Security Policy (CSP) headers as defense-in-depth measures for form fields.
Adobe Experience Manager 6.5.23.0 or later, or Adobe Experience Manager 2025.5.0 or later
- Backup the current AEM instance and associated content repositories before initiating any upgrade
- Review the Adobe Experience Manager 6.5.23.0 (or 2025.5.0) release notes and known issues documentation on helpx.adobe.com for any specific migration or compatibility requirements
- Test the upgrade in a non-production/staging environment first to ensure compatibility with custom code and integrations
- Ensure all third-party bundles and custom components are compatible with the target version
- Execute the upgrade following Adobe's official upgrade documentation for AEM 6.5 or the cloud service version as applicable
- After upgrade, verify that the stored XSS vulnerability in form fields is resolved by testing the affected input fields
- Clear AEM caches and rebuild any search indexes if required post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47003 — 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-47003 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