CVE-2026-48304
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. A low-privileged attacker can inject malicious JavaScript payloads into vulnerable input fields, which execute when other users browse to pages containing those fields. 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.
-
Identify the installed Adobe Experience Manager versionAccess the AEM Welcome page (usually at /aem/start.html) or check the product.info via the system console at /system/console/product. Look for the version number displayed.Affected if The version is 6.5.24 or earlier in the 6.5.x line, or 2026.04 or earlier in the 2026.x line, or specifically shows version 6.5 without a service pack beyond 24.
-
Determine if AEM Forms module is deployedCheck if the Forms add-on is installed by navigating to /libs/forms/ or by looking for Forms-related packages in the Package Manager at /crx/packmgr. The vulnerability affects form fields specifically.Affected if The Forms module is installed and accessible, allowing users to create or interact with forms.
-
Verify user permission levels for form accessReview the user groups and permissions in AEM at /useradmin. Check whether low-privileged users (such as those in the 'contributors' or 'authors' group with limited permissions) have access to create or edit form content.Affected if Low-privileged users have the ability to create or modify form fields in AEM Forms.
-
Inspect form field configuration for input validationNavigate to any existing Adaptive Forms or Form Fragments in AEM at /content/forms/af. Open a form in Edit mode and inspect the field properties under the Patterns or Validation tabs to see if server-side input validation or output encoding is configured.Affected if Form fields lack input validation rules or output encoding is not applied to the field data bindings.
You are affected if your AEM installation version is 6.5.24 or earlier, 2026.04 or earlier, or shows version 6.5 without the 6.5.25+ update, AND low-privileged users can access and modify form fields that are rendered on public or other user-accessible pages.
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/sanitization on all form fields in AEM, particularly those accepting user-generated content. Apply AEM security hotfixes or upgrade to a patched version.
AEM 6.5.25.0 or later; AEM 2026.5.0 or later
- Verify current Adobe Experience Manager version in use (check /system/console or AEM startup log)
- Review the Adobe Experience Manager 6.5.25 release notes and 2026.5.0 release notes for compatibility requirements
- Ensure all custom code and third-party integrations are compatible with the target version
- Create a full backup of the AEM repository (crx-quickstart) and database
- Perform a staged upgrade in a non-production environment first
- Test custom applications and workflows on the upgraded environment
- Schedule a maintenance window for the production upgrade
- Apply the service pack or upgrade to the fixed version (6.5.25.0+ or 2026.5.0+)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48304 — 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-48304 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