CVE-2026-48301
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 · high confidenceAdobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. Low-privileged attackers can inject malicious JavaScript that persists in the system and executes in victims' browsers when they view pages containing the affected form fields. The CVSS scope changed indicates the impact extends beyond the vulnerable component.
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.
-
Identify installed AEM versionAccess the AEM System Information console at /system/console/info or check the product version from the AEM Welcome page footer. In the OSGi Felix Console, navigate to the 'Info' tab to view the product version details.Affected if The installed version is 6.5.24 or earlier in the 6.5.x line, any version in the 2026.0x line prior to 2026.5.0, or labeled as LTS SP1 matching those ranges.
-
Confirm AEM forms feature is in useCheck if Adaptive Forms, Core Components with form containers, or custom form implementations are deployed. Navigate to /libs/fd/fdm/forms in the repository or check the forms console at /aem/forms to enumerate active form configurations.Affected if Any form-based functionality (Adaptive Forms, Form Fragments, or custom form components) is enabled and accessible to users.
-
Identify if low-privileged users can access form authoringReview user group permissions in AEM Groups (http://localhost:4502/libs/granite/security/content/graniteusers.html) and verify if standard users or custom groups with limited privileges have create, modify, or contributor access to form content in /content or /apps paths.Affected if Users with low-privileged roles (non-admin) have write access to form fields or form content creation capabilities.
-
Inspect form field data for persisted scriptsIf forms are in use, examine the stored form data or content fragments in the CRX/DE repository under /content/dam/forms or /content/forms for any unexpected script tags, JavaScript event handlers (onerror, onload, onclick), or encoded payloads that may indicate stored XSS.Affected if Form submissions or saved form data contains unescaped HTML script elements or JavaScript event handlers in input fields.
You are affected if your AEM version falls within the ranges of 6.5.x prior to 6.5.25.0 or 2026.x prior to 2026.5.0, and your environment exposes form fields to authenticated users with low privileges.
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
Apply available Adobe patches for AEM to address the vulnerability, and implement output encoding/sanitization on form fields along with Content Security Policy headers to mitigate XSS risks.
AEM 6.5.25.0 (LTS) or AEM 2026.5.0
- Identify current Adobe Experience Manager version by checking the AEM welcome page or system console
- For AEM 6.5.x LTS versions: Plan upgrade to AEM 6.5.25.0 or later
- For AEM 2026.x versions: Plan upgrade to 2026.5.0 or later
- Schedule maintenance window for the upgrade process
- Backup the current AEM instance including repository, database, and configuration files
- Review Adobe's official upgrade documentation for AEM 6.5.25 or 2026.5.0 respectively
- Execute upgrade following Adobe's recommended upgrade procedure
- Verify the upgrade was successful by checking version in AEM welcome page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48301 — 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-48301 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