dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46983

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

A stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged attackers to inject malicious JavaScript into vulnerable form fields. The malicious payload persists in the system and executes when users view pages containing the compromised fields.

MitigationApply Adobe's official security patch by upgrading AEM to version 6.5.23 or later after validating compatibility in a non-production environment.

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 installed AEM version
    Access the AEM Web Console (Go to /system/console/configMgr and look for 'Adobe Experience Manager Version' in the About Adobe Experience Manager section), or check the version file in the installation directory. Alternatively, request the JSON endpoint at /libs/granite/core/content/login.json or check the welcome page footer.
    Affected if The installed version is earlier than 6.5.23.0 or earlier than 2025.5.0 (the version shown is below the patched releases)
  2. Confirm Forms or Adaptive Forms module is in use
    Navigate to the AEM Forms interface at /aem/forms or check if the forms.webservices configuration exists in the OSGi config manager at /system/console/configMgr. Look for packages with 'forms' in the name under /system/console/bundles.
    Affected if The Forms or Adaptive Forms module is installed and accessible to users
  3. Identify exposed form endpoints
    Check for accessible form-related URLs in the publish instance, such as /content/forms/af/, /bin/form/..., or custom form paths. Use CRX/DE (accessible at /crx/de) to search for form content nodes under /content/forms/ and verify they are published and accessible.
    Affected if Form content nodes exist under /content/forms/ and are published to the publish instance
  4. Verify form field input validation configuration
    Inspect form field components in CRX/DE under /libs/fd/af/components or custom form component paths. Check whether XSS protection rules are defined in the form field's 'validation' properties or in the overall form submission configuration.
    Affected if Form fields do not have XSS validation rules configured or the validation can be bypassed by low-privileged users

Your environment is affected if the installed AEM version is below 6.5.23.0 or below 2025.5.0 AND Forms/Adaptive Forms are enabled and accessible to users who can submit content to form fields.

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

Apply Adobe's official security patch by upgrading AEM to version 6.5.23 or later after validating compatibility in a non-production environment.

Recommended fix High confidence

AEM 6.5.23.0 or later for 6.5.x line; AEM 2025.5.0 or later for 2025.x line

  1. 1. Back up your current AEM instance including repository, database, and configuration files
  2. 2. Review Adobe Experience Manager 6.5.23.0 release notes for any migration or compatibility requirements
  3. 3. Test the upgrade in a non-production environment before deploying to production
  4. 4. Run the upgrade following Adobe's standard AEM upgrade procedure for your deployment type
  5. 5. Verify that the Forms or form-based components function correctly after upgrade
  6. 6. Validate that no custom code depends on vulnerable behavior that may have changed
Caveat Review release notes for deprecation notices; custom form components may require testing for compatibility with the fixed version

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46983 — 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-46983 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