CVE-2025-47078
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 payloads that persist in the system and execute in victim browsers when they navigate to pages containing the affected 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.
-
Check installed AEM versionAccess the AEM Web Console or system information page (typically at /system/console or /crx/packmgr/list.jsp) to retrieve the exact version number of the Adobe Experience Manager installationAffected if The installed version is below 6.5.23.0 for the 6.x release line, or below 2025.5.0 for the 2025 release line
-
Identify AEM release lineDetermine whether the installation is on the long-term service pack (6.x) release line or the year-based (2025.x) release line by examining the version format shown in the system informationAffected if The system is on either release line and the version falls below the corresponding safe threshold
-
Locate form field componentsReview the AEM Forms or Adaptive Forms components deployed in the system. Check content fragments, experience fragments, or custom form models that contain input fields accepting user dataAffected if Form components with input fields exist in the system and the AEM version is vulnerable
-
Inspect stored form dataQuery the JCR (Java Content Repository) or examine form submission data in the AEM repository under /content/forms or similar content paths to review any stored values in form fieldsAffected if Form field data exists in the repository and the installed AEM version is within the affected range
A system is affected if it runs Adobe Experience Manager version 6.5.22 or earlier (6.x line) or any version before 2025.5.0 (2025 line), and contains form fields that accept user input where malicious scripts could be stored and executed.
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, implement robust input validation and output encoding on vulnerable form fields, and configure Content Security Policy headers to mitigate XSS execution.
AEM 6.5.23.0 or AEM 2025.5.0 (or later)
- Identify the current Adobe Experience Manager version in use
- If running version 6.5.22 or earlier, upgrade to version 6.5.23.0 or later
- If running version 2025.4 or earlier (2024.x, 2025.0-2025.4), upgrade to version 2025.5.0 or later
- After upgrade, verify the fix by testing form fields for XSS vulnerability remediation
- 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.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47078 — 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-47078 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