CVE-2025-47055
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 scripts into vulnerable form inputs, which persists in the system. When other users view pages containing these compromised form fields, the malicious script executes in their browsers, potentially enabling session hijacking, data theft, or further propagation.
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.
-
Verify AEM versionAccess the AEM System Information console or check the version.properties file in the crx-quickstart directory. Compare the installed version against the affected ranges: versions before 6.5.23.0 or before 2025.5.0 are vulnerable.Affected if The installed version is less than 6.5.23.0 or less than 2025.5.0
-
Identify exposed form componentsReview the AEM instance for use of form components (such as Adaptive Forms, Foundation Form, or custom form implementations) that accept user input and store data in the repository.Affected if Form components that accept and store user-supplied input are present and accessible to low-privileged users
-
Inspect form field input validationExamine the form field configurations in the AEM Forms or Foundation component settings. Check whether input validation and output encoding settings are properly configured to prevent script injection.Affected if Form fields lack proper input validation or output encoding, allowing unsanitized content to be stored
-
Search for existing malicious contentQuery the AEM repository (via CRXDE, AEM Developer Tools, or a repository search) for script tags or JavaScript syntax in form-related content nodes. Focus on form submission data, form field default values, and form container metadata.Affected if Script tags or JavaScript code are found stored in form field data within the repository
If the AEM version is before 6.5.23.0 or before 2025.5.0 AND form components with user input are exposed, the environment is affected by this stored XSS vulnerability.
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. Alternatively, apply the specific security patch provided by Adobe for this vulnerability and validate that form input validation properly sanitizes user-supplied content.
Adobe Experience Manager 6.5.23.0 or later (6.5.x train) / 2025.5.0 or later (2025 train)
- 1. Identify current Adobe Experience Manager version by navigating to /system/console/bundles or checking the About Adobe Experience Manager page
- 2. Schedule a maintenance window for the upgrade procedure
- 3. Perform a full backup of the AEM instance including repository, database, and configuration files
- 4. Upgrade Adobe Experience Manager to version 6.5.23.0 or later (or 2025.5.0 or later for the new release train)
- 5. After upgrade, clear the AEM repository cache and rebuilt any search indexes as needed
- 6. Verify the upgrade was successful by checking the AEM version and confirming core functionality works
- 7. Test the previously vulnerable form fields to confirm the XSS vulnerability is remediated
- 8. Monitor logs for any post-upgrade errors or anomalies
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47055 — 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-47055 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