CVE-2025-46919
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged authenticated users to inject malicious JavaScript into form fields. The injected payload persists in the system and executes in victim users' browsers when they access pages containing the compromised form fields.
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.
-
Check Adobe Experience Manager versionNavigate to AEM Welcome page > Tools > Operations > Diagnosis > Version Info, or inspect the version.properties file in the crx-quickstart folder, or run: java -jar aem-quickstart.jar -versionAffected if Installed version is 6.5.22 or earlier, or below 2025.5.0
-
Verify presence of low-privileged authenticated usersAccess AEM User Console at /security/users.html or /libs/cq/security/content/useradmin and review user accounts with limited permissions (authors, contributors, or custom groups with form submission access)Affected if Low-privileged authenticated users exist who can access form submission features
-
Identify form components that store user inputReview AEM Forms or Adaptive Form configurations in /libs/fd/af or /apps for form fields that persist data to the repository without validation, or check Content Fragments with form field componentsAffected if Form components that accept and store user-submitted data are enabled in the environment
-
Search repository for suspicious stored scriptsUse CRXDE Lite (crx/de) or a JCR query to search nodes under /content for XSS payloads: query for string patterns like '<script', 'javascript:', 'onerror=', 'onload=' in form submission data or in content nodes under /contentAffected if Malicious script tags or event handlers are found stored in form field data or content repositories
Environment is affected if AEM version is below 6.5.23.0 or 2025.5.0 AND the system allows low-privileged users to submit and store content in form fields.
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 Adobe Experience Manager to version 6.5.23 or later, which contains the vendor security patch addressing this vulnerability.
Adobe Experience Manager 6.5.23.0 (for 6.5.x line) or 2025.5.0 (for newer release train)
- Identify the current Adobe Experience Manager version running in your environment
- If running AEM 6.5.x release line: Plan upgrade to version 6.5.23.0 or later
- If running AEM as a Cloud Service or newer release train: Plan upgrade to version 2025.5.0 or later
- Schedule maintenance window for the upgrade following Adobe's recommended upgrade best practices
- Perform the upgrade in a non-production environment first to validate compatibility
- After upgrading to the fixed version, verify that the stored XSS vulnerability is no longer present
- Test that affected form fields function correctly post-upgrade
- Deploy the upgraded version to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46919 — 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-46919 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