CVE-2025-46848
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 · high confidenceAdobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. Low-privileged attackers can inject malicious JavaScript payloads into vulnerable form inputs, which persist in the system. When authenticated users browse to pages containing the affected fields, the injected scripts execute in their browsers, potentially enabling session hijacking, credential theft, or further privilege escalation.
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.
-
Verify Adobe Experience Manager versionAccess the AEM Welcome page and navigate to Tools > Operations > Diagnosis, or access /system/console/about in the URL to retrieve the installed AEM version. Compare this version against the affected ranges: versions below 6.5.23.0 and versions below 2025.5.0.Affected if The installed AEM version is 6.5.22 or earlier, or falls below 2025.5.0.
-
Confirm AEM Forms or form components are in useNavigate to the AEM Forms interface (typically at /aem/forms) or inspect the page templates and components used in your AEM instance for Form components. Check the package manager or system console for installed AEM Forms packages.Affected if AEM Forms or form-based components are installed and actively used on the instance.
-
Inspect form field data in the JCR repositoryUse the CRXDE Lite tool (accessible at /crx/de) or the AEM Query Builder to search through content nodes under /content for form-related nodes (typically under /content/forms). Examine the values stored in form input nodes for suspicious script tags, javascript: URIs, or event handler attributes.Affected if Form data in the repository contains unescaped script tags, javascript: protocols, or HTML event handlers in field values.
-
Review HTML output of forms for unencoded contentAccess pages containing form fields as a regular user would. Use browser developer tools to view the page source and inspect form input values, labels, and error messages. Look for unescaped HTML characters or raw script content rendered in attributes or text nodes.Affected if Form fields render raw HTML, JavaScript, or event handler attributes without proper encoding.
A user is affected if their AEM version is below 6.5.23.0 or below 2025.5.0 AND they have forms or form inputs in use that contain or render unescaped script content.
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.22 or later, or apply the corresponding security patch. Implement strict input validation and output encoding for all form fields as a defense-in-depth measure.
AEM 6.5.23.0 or later, or AEM 2025.5.0 or later
- Review Adobe Experience Manager upgrade documentation at helpx.adobe.com for your current version
- Create a complete backup of your AEM instance including repository, database, and configurations
- Set up a staging/test environment running the current production version
- Test the upgrade to version 6.5.23.0 (for 6.x branch) or 2025.5.0 (for cloud/2024+ branch) in the staging environment
- Verify all custom code, integrations, and workflows function correctly after upgrade
- Apply any additional post-upgrade steps recommended in Adobe's release notes
- Deploy the validated upgrade to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46848 — 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-46848 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