dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-54247

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to after 2025.8.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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.23.0 and earlier are affected by an Improper Input Validation vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized read access.

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.23.0 and earlier contain an improper input validation vulnerability that allows low-privileged attackers to bypass security controls and gain unauthorized read access to sensitive data. The vulnerability stems from insufficient validation of user input that can be manipulated to circumvent access restrictions.

MitigationApply the vendor-supplied security patch for Adobe Experience Manager to address the input validation flaw, or upgrade to a patched version. Verify that access control policies properly enforce read restrictions for low-privileged users after remediation.

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.8.0= 6.5

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Adobe Experience Manager version
    Check the AEM product version through the system console or version file. Access the Help menu in AEM or check the crx-quickstart folder for version information.
    Affected if The installed version is 6.5.23.0 or earlier, any 6.5.x version, or version 2025.8.0 or earlier.
  2. Confirm AEM edition and build
    Verify the exact build number and edition through the AEM System Information console at /system/console/configMgr or by checking the version.properties file in the installation directory.
    Affected if The build version falls within the affected ranges (<= 6.5.23.0 or <= 2025.8.0).
  3. Review user account privileges
    Enumerate existing AEM user accounts and their assigned groups/permissions through the User Management console at /libs/granite/security/content/useradmin.html or via the UserManager API.
    Affected if There are low-privileged user accounts configured with limited access that could potentially exploit input validation gaps.
  4. Audit access control configuration
    Examine the repository-level ACLs and permission configurations in AEM under /etc/repoaccess or through the Granite Access Control Management console to verify read restrictions on sensitive paths.
    Affected if Read access controls can be bypassed or are insufficiently enforced for non-admin users.

A user is affected if their AEM installation version is 6.5.23.0 or earlier, 6.5.x, 2025.8.0 or earlier, and low-privileged users exist who could potentially exploit the input validation bypass to access sensitive data.

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 a release after 2025.8.0
Interim mitigation

Apply the vendor-supplied security patch for Adobe Experience Manager to address the input validation flaw, or upgrade to a patched version. Verify that access control policies properly enforce read restrictions for low-privileged users after remediation.

Recommended fix Moderate confidence

AEM 6.5 Service Pack 24 or later / Latest available AEM 6.5 service pack

  1. 1. Identify the current Adobe Experience Manager version by checking the AEM welcome page or system console (/system/console/status), then confirm it is 6.5.23.0 or earlier
  2. 2. Navigate to the Adobe Experience Manager security bulletins page at helpx.adobe.com for the latest security patches
  3. 3. Download and apply the latest AEM service pack or cumulative fix pack that addresses this vulnerability (typically named like 'AEM 6.5 Service Pack X' or 'Cumulative Fix Pack')
  4. 4. Before applying to production, test the patch in a non-production environment to verify functionality
  5. 5. After applying the patch, restart the AEM instance as instructed by the patch documentation
  6. 6. Verify the patch was applied successfully by checking the AEM version again and confirming the security fix is in place
Caveat Adobe service packs typically include backward-compatible fixes; however, custom code interacting with the fixed input validation should be tested

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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