CVE-2026-48300
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.24, LTS SP1, 2026.04 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. Scope is changed.
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager allows low-privileged users to inject malicious JavaScript into form fields. When other users view pages containing these compromised fields, the injected script executes in their browsers. The scope change indicates the vulnerability impacts components beyond the vulnerable form itself.
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.25.0< 2026.5.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.
-
Check installed AEM versionAccess the AEM Welcome page (/aem/start.html) or the System Information console (/system/console/status-productinfo) to view the installed product version. Compare this version number against the affected ranges: versions before 6.5.25.0, before 2026.5.0, or any 6.5.x release.Affected if The installed version is less than 6.5.25.0, less than 2026.5.0, or any 6.5.x variant.
-
Identify form fields accepting user inputReview your AEM Forms implementations, Adaptive Forms, or custom form components that accept user-submitted content. Check both authored forms and any forms created by low-privileged users.Affected if Forms exist where low-privileged users can create or edit form field configurations or submit content.
-
Audit user permissions for form creationNavigate to the User Administration console (/security/users.html or /security/groups.html) and review which user groups have permissions to create, edit, or submit form content. Identify any groups with reduced privileges that interact with forms.Affected if Low-privileged users (non-admin) have access to create or modify form fields or submit content to forms.
-
Inspect form field content for malicious scriptsUse the AEM Query Builder or CRX/DE Lite (/crx/de) to search form content nodes (typically under /content/forms or /content/dam/forms) for suspicious patterns like <script>, javascript:, onerror=, or other XSS vectors in field values.Affected if Stored XSS payloads or unexpected script tags are found in form field content nodes.
-
Review Content Security Policy headersCheck your dispatcher configuration or AEM HTML Library Manager settings for Content-Security-Policy headers. Verify if inline scripts are restricted or if forms have CSP protections in place.Affected if No CSP headers are configured, or CSP allows inline scripts on form pages, providing no defense-in-depth.
You are affected if your AEM version is below 6.5.25.0 or 2026.5.0 AND low-privileged users can create or submit content to form fields in your environment.
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.25.02026.5.0
Implement output encoding and input validation for all form fields in AEM; apply vendor patches when available (upgrade from affected versions 6.5.24/LTS SP1/2026.04 to fixed releases).
AEM 6.5.25.0 (LTS) or AEM 2026.5.0 (cloud release) depending on deployment track
- 1. Identify the current Adobe Experience Manager version in use (either 6.5.x or 2026.x release line)
- 2. For AEM 6.5 LTS deployments: Plan upgrade to version 6.5.25.0 or later
- 3. For AEM 2026 cloud deployments: Plan upgrade to version 2026.5.0 or later
- 4. Review Adobe's official upgrade documentation at helpx.adobe.com for detailed upgrade procedures
- 5. Test the upgrade in a non-production environment before deploying to production
- 6. Perform a full backup of the current AEM instance before upgrading
- 7. Execute the upgrade following Adobe's recommended upgrade path
- 8. Verify the upgrade was successful and test that the XSS vulnerability is no longer present
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-2026-48300 — 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-2026-48300 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