CVE-2025-46990
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 · moderate confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. When victims view pages containing the compromised fields, the malicious script executes in their browsers.
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.
-
Determine your AEM versionLog in to AEM as administrator and navigate to the Welcome page, or check the version.properties file in the crx-quickstart folder. Alternatively, access the System Information console at /system/console/systeminfoAffected if The installed version is 6.5.22 or earlier, or falls below 2025.5.0 for the newer release line
-
Identify AEM Forms usageCheck if the AEM Forms module is installed and enabled. Navigate to Forms in the AEM navigation panel, or check for form assets in the /content/forms folder via CRXDE Lite at /crx/deAffected if AEM Forms is installed and forms are being used to collect user input
-
Verify low-privileged user access to formsCheck user group permissions in AEM at /useradmin. Look for groups with contributor or author-level access that have permission to create or edit form submissionsAffected if Low-privileged users (non-administrators) have access to create or edit form content
-
Audit existing form submissions for suspicious contentAccess form submissions through AEM Inbox, Forms workflow, or query the repository at /content/forms/submissions for any entries containing script tags, javascript:, or event handlers like onload/onerrorAffected if Form submissions contain unsanitized HTML, script tags, or JavaScript event handlers that could execute in victim browsers
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND you have AEM Forms enabled with low-privileged users who can submit form 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
Apply the available AEM security patch to upgrade beyond version 6.5.22. Additionally, audit existing form submissions for injected scripts and implement output encoding as a defense-in-depth measure.
AEM 6.5.23.0 (for 6.5.x releases) or AEM 2025.5.0 (for Cloud Service)
- Back up the current AEM instance including the content repository, configuration, and any custom code
- Review the release notes for AEM 6.5.23.0 (for 6.5.x customers) or 2025.5.0 (for Cloud Service) to understand changes and potential impacts
- Test the upgrade in a non-production environment before deploying to production
- Ensure custom components or forms that accept user input are reviewed for compatibility with the new version
- Apply the upgrade following Adobe's standard AEM upgrade procedures
- After upgrade, verify that the XSS protection is working correctly by testing form inputs with typical XSS payloads
- Monitor the system after deployment for any unexpected behavior
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46990 — 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-46990 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