dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46943

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 6.5.23.0 / 2025.5.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Adobe 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 confidence

Adobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where low-privileged authenticated users can inject malicious JavaScript into form fields. The injected script executes in the browser of any user who views the compromised page containing the affected field.

MitigationImplement input validation and output encoding for all form fields in AEM; apply the vendor security patch when released. Review and sanitize existing user-generated content in the system.

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
Experience ManagerApplication
Affected:< 6.5.23.0< 2025.5.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify AEM version
    Access the AEM Welcome page or Help menu and navigate to 'About Adobe Experience Manager' to view the installed version number. Alternatively, locate the version manifest file in the AEM installation directory.
    Affected if The displayed version is earlier than 6.5.23.0 or earlier than 2025.5.0 (for the newer release track)
  2. Confirm release track
    Determine whether the installation follows the quarterly service pack release model (6.5.x series) or the year-based release model (2025.x series) by reviewing the version string format.
    Affected if The installation uses either the 6.5.x or 2025.x release track with a version number below the fixed releases
  3. Verify low-privilege user access
    Review user group memberships and permissions in the AEM User Management console to confirm whether standard authenticated users without administrator privileges can access and modify form content.
    Affected if Standard authenticated users have permission to create or edit pages containing form fields, as the vulnerability allows these low-privilege users to inject malicious scripts
  4. Inspect form field configuration
    Examine the Form components and their associated validation or encoding settings within the AEM Forms or Core Components configuration. Look for whether output encoding is explicitly disabled or uses unsafe input handling.
    Affected if Form fields are configured without proper input validation or output encoding protections enabled

Your environment is affected if the installed AEM version is below 6.5.23.0 or below 2025.5.0 and your system allows low-privileged authenticated users to create or edit form content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.5.23.0 / 2025.5.0 or later
Fixed in 6.5.23.02025.5.0
Interim mitigation

Implement input validation and output encoding for all form fields in AEM; apply the vendor security patch when released. Review and sanitize existing user-generated content in the system.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 or later; Adobe Experience Manager 2025.5.0 or later

  1. Identify your current Adobe Experience Manager version by checking the product console or system information
  2. Download Adobe Experience Manager 6.5.23.0 (or later) from the Adobe distribution center or apply the 2025.5.0 (or later) release for newer release tracks
  3. Review the Adobe Experience Manager release notes and known issues before upgrading
  4. Perform a full backup of your AEM instance including the repository, configuration, and custom code
  5. Test the upgrade in a non-production environment first
  6. Apply the upgrade following Adobe's standard upgrade procedures
  7. After upgrading, verify that the stored XSS vulnerability is remediated by testing the previously vulnerable form fields
Caveat Review release notes for potential compatibility issues with custom components or third-party integrations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46943 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46943 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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