CVE-2025-47067
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious payload persists on the server and executes in victims' browsers when they view pages containing the affected 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.
-
Check installed AEM versionNavigate to the AEM Welcome page and locate the version information, or query the system console (/system/console/configMgr) for the AEM version bundle. Compare the version number against 6.5.23.0 and 2025.5.0.Affected if The installed version is earlier than 6.5.23.0 (for 6.5.x branches) or earlier than 2025.5.0 (for newer branches).
-
Verify Forms module is enabledCheck if Adobe Experience Manager Forms is installed and enabled by navigating to the AEM Tools console or querying the package manager for 'aem-forms' packages.Affected if Forms module is present and enabled, as this vulnerability targets form field injection.
-
Inspect form field configurations for malicious payloadsReview form definitions in the repository under /content/forms or /apps, and check form field properties for suspicious script tags or event handlers in value/placeholder attributes.Affected if Any form field configuration contains unsanitized script content or event handlers like onload, onerror, or javascript: URIs.
-
Review recent form submission logsExamine AEM audit logs or form submission records for patterns indicating automated or suspicious form submissions containing HTML/script content.Affected if Logs show form submissions with script tags or HTML injection attempts from low-privileged user accounts.
You are affected if your AEM version is below 6.5.23.0 (6.5.x branch) or below 2025.5.0 AND the Forms module is enabled, allowing stored XSS payloads in form fields to persist and execute.
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 apply the security patch. Implement input validation and output encoding on all form fields as a defense-in-depth measure.
AEM 6.5.23.0 or later (on-premise); AEM as a Cloud Service 2025.5.0 or later
- 1. Identify your current Adobe Experience Manager version by checking the product information or system console.
- 2. For AEM 6.5 on-premise: Upgrade to version 6.5.23.0 or later.
- 3. For AEM as a Cloud Service: Upgrade to version 2025.5.0 or later.
- 4. After upgrading, verify that the XSS vulnerability is remediated by testing the form fields mentioned in the security bulletin.
- 5. Ensure the upgrade is tested in a non-production environment before deploying to production.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.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 $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47067 — 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-47067 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