CVE-2025-64827
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.23 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.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where low-privileged attackers can inject malicious JavaScript into vulnerable form fields. When victims browse to pages containing these compromised fields, the injected scripts execute in their browsers, enabling session hijacking, credential theft, or defacement.
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.24.0< 2025.12.0= 6.5CVSS 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 System Information console or check the version.properties file in the crx-quickstart directory. The version is typically displayed on the Welcome screen under 'Version' or accessible via the /system/console/configMgr/com.adobe.granite.infoprovider endpoint.Affected if The installed version is 6.5.x where x is 23 or lower; or the version string starts with 6.5 (without a decimal version number); or the version is any 2025 release before 2025.12.0.
-
Verify form field accessibilityNavigate to the content management interface where form components are created or edited. Identify if the vulnerable form fields are present in any published or preview-enabled content fragments or Adaptive Forms.Affected if Form fields that accept user input are present and accessible without additional configuration changes from default settings.
-
Confirm low-privileged user access to form editingLog in with a standard authenticated user account (such as a member of the 'authors' group) and verify permission to create or edit form content in either the Classic UI, Touch UI, or Forms workflow.Affected if Low-privileged users with standard authoring permissions can access and modify form components without elevated admin rights.
-
Inspect stored form submissions for unencoded inputUse CRXDE Lite or the Content Explorer to navigate to the repository path where form data is stored (commonly under /content or /var). Examine stored values in form fields to see if raw HTML or script tags are persisted without encoding.Affected if Form field values are stored and retrieved without server-side output encoding applied, visible as raw script or HTML tags in the repository.
A user is affected if their AEM installation version is 6.5.23 or earlier, 6.5 (any decimal), or any 2025 release before 2025.12.0, AND the system has form fields accessible to low-privileged users that accept and store unsanitized input.
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.24.02025.12.0
Upgrade Adobe Experience Manager to version 6.5.24 or later. Until patched, implement output encoding on all form fields and consider deploying a WAF with XSS rules to mitigate exploitation.
AEM 6.5.24.0 or later (6.5.x line); AEM as a Cloud Service 2025.12.0 or later
- Verify current Adobe Experience Manager version in use (check /system/console/bundles or AEM Welcome page)
- Create a full backup of the AEM repository (crx-quickstart) and database
- Test the upgrade in a non-production environment before deploying to production
- Install Adobe Experience Manager 6.5.24.0 or later for 6.5.x deployments, or migrate to 2025.12.0 or later for AEM as a Cloud Service
- After upgrade, verify that the stored XSS vulnerability is no longer present by testing form field inputs with script payloads
- Confirm normal AEM functionality works as expected (authoring, publishing, workflow execution)
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-64827 — 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-64827 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