Experience ManagerApplication · Adobe

CVE-2023-29307

MEDIUM · 5.4 CVSS v3.1 Published 2023-06-15
Fix available
A fix is available. Upgrade to 6.5.17.0 / 2023.4 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.16.0 (and earlier) is affected by a URL Redirection to Untrusted Site ('Open Redirect') vulnerability. A low-privilege authenticated attacker could leverage this vulnerability to redirect users to malicious websites. Exploitation of this issue requires user interaction.

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.16.0 and earlier contain an open redirect vulnerability where a low-privilege authenticated attacker can manipulate URL parameters to redirect users to malicious external websites. Exploitation requires user interaction, such as clicking a crafted link.

MitigationUpgrade Adobe Experience Manager to version 6.5.17.0 or later. Additionally, implement URL validation and filtering on the application layer to prevent untrusted redirects.

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.17.0
Experience Manager Cloud ServiceApplication
Affected:< 2023.4

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 deployment type and version
    Locate the installed Adobe Experience Manager version in the system administration console, about page, or version manifest file. For AEM Cloud Service, check the release version in the Cloud Manager or environment details.
    Affected if The installed version is AEM 6.5.16.0 or earlier, or AEM Cloud Service version is 2023.3 or earlier.
  2. Verify the redirect parameter functionality is accessible
    Determine if the application exposes URL redirection functionality that accepts external parameters. Test by observing which URL parameters control redirect behavior in common AEM paths (such as login, logout, or content paths with redirect parameters).
    Affected if The application accepts redirect parameters without proper validation, allowing arbitrary external URLs.
  3. Confirm authentication requirements for the vulnerable endpoint
    Review the authentication configuration for the redirect functionality. Check if low-privilege users can access the endpoint that processes redirect parameters.
    Affected if The redirect endpoint is accessible to low-privilege authenticated users without additional authorization checks.
  4. Inspect URL validation configuration
    Examine the application's URL validation rules, filter configurations, or security context settings that govern allowed redirect destinations. Look for patterns that allow or block external domains in redirect parameters.
    Affected if No URL validation exists, or validation permits untrusted external domains in redirect parameters.

You are affected if your AEM version is below 6.5.17.0 (or Cloud Service below 2023.4) AND the application allows redirect parameters without validating that the destination is a trusted internal URL.

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.17.0 / 2023.4 or later
Fixed in 6.5.17.02023.4
Interim mitigation

Upgrade Adobe Experience Manager to version 6.5.17.0 or later. Additionally, implement URL validation and filtering on the application layer to prevent untrusted redirects.

Recommended fix High confidence

AEM 6.5.17.0 (on-premise) or AEM Cloud Service 2023.4

  1. 1. For Adobe Experience Manager (on-premise): Upgrade to version 6.5.17.0 or later
  2. 2. For Adobe Experience Manager Cloud Service: Upgrade to version 2023.4 or later
  3. 3. After upgrading, verify the open redirect vulnerability is resolved by testing the affected endpoints

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29307 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-29307 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