CVE-2025-47082
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 · moderate confidenceAdobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability. A low-privileged attacker can inject malicious JavaScript into form fields, which persists in the system. When users view pages containing these compromised form fields, the malicious script executes in their browsers, potentially enabling session hijacking or data theft.
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 installed AEM versionAccess the AEM Web Console (typically at /system/console/config) or check the crx-quickstart/packageinfo.xml file for the exact version number. Alternatively, run: curl -s https://your-aem-host:port/libs/granite/core/content/login.html 2>/dev/null | grep -o 'version-[0-9.]*' or check the bundled product version in the OSGi console.Affected if The version is below 6.5.23.0 or below 2025.5.0, meaning it falls within the affected ranges.
-
Determine if AEM Forms or custom forms are configuredNavigate to the AEM Forms console at /aem/forms or check for form-based workflows under /content/forms in the CRX/DE repository at /apps or /content. Inspect whether any Adaptive Forms, Foundation Forms, or custom form components are present.Affected if Form functionality is enabled and contains user-editable form field definitions in the system.
-
Inspect form data for unsanitized inputUsing CRX/DE (accessible at /crx/de), navigate to form submission data stores typically under /content/forms/submissions or /var/forms and search form field nodes for script tags, javascript: URIs, or HTML event handlers (onclick, onerror, etc.). Use XPATH query or grep through stored form data.Affected if Form fields contain unsanitized script tags, event handlers, or javascript: payloads that could execute in a user's browser.
-
Review low-privileged user access to form editingCheck AEM user group permissions in the User Administration console (/security/users.html or /libs/cq/security/content/admin.html). Verify which groups have write access to form content paths under /content/forms or /apps.Affected if Low-privileged users (non-admin) have write permissions to form definitions or form submission data, allowing them to inject malicious content.
Your environment is affected if the AEM version is below 6.5.23.0 or below 2025.5.0 AND forms are in use with editable fields that could accept user-supplied content without sanitization.
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 to Adobe Experience Manager version 6.5.23 or later to obtain the security patch. After upgrading, verify that all form fields properly sanitize user input to prevent XSS.
AEM 6.5.23.0 or later; AEM as a Cloud Service 2025.5.0 or later
- Identify your current Adobe Experience Manager version and deployment type (on-premise 6.5.x or AEM as a Cloud Service)
- For AEM 6.5.x on-premise: Plan and schedule upgrade to version 6.5.23.0 or later
- For AEM as a Cloud Service: Plan and schedule upgrade to version 2025.5.0 or later
- Perform the upgrade following Adobe's official upgrade documentation
- After upgrade, verify the version has been updated successfully
- Test the formerly vulnerable form fields to confirm the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47082 — 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-47082 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