Experience ManagerApplication · Adobe

CVE-2023-22263

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-22
Fix available
A fix is available. Upgrade to 6.5.16.0 / 2023.1.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
Experience Manager versions 6.5.15.0 (and earlier) are 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.15.0 and earlier contain an open redirect vulnerability that allows a low-privilege authenticated attacker to craft malicious URLs that redirect users to arbitrary external websites. Exploitation requires user interaction, such as clicking a crafted link.

MitigationApply Adobe's security update (version 6.5.16.0 or later) or install the corresponding security patch to remediate the open redirect vulnerability.

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.16.0
Experience Manager Cloud ServiceApplication
Affected:< 2023.1.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. Check AEM version via Help menu
    Log into AEM as administrator and navigate to Help > About Adobe Experience Manager, or access /libs/granum/ui/settings.xml if available, to view the exact version number
    Affected if The displayed version is 6.5.15.0 or earlier for on-premise AEM, or the version cannot be confirmed as 6.5.16.0 or later
  2. Check AEM version via Web Console
    Access the Adobe Experience Manager Web Console at /system/console/product and locate the Version field in the Product Information section
    Affected if The version shown is earlier than 6.5.16.0 for AEM on-premise installations
  3. Check AEM Cloud Service version
    Access the Cloud Service admin interface or check the version information via the AEM SDK console at /libs/cq/core/content/versioninfo to determine the release version
    Affected if The Cloud Service version is earlier than 2023.1.0
  4. Verify version against affected ranges
    Compare your installed version number to the affected ranges: AEM on-premise < 6.5.16.0 or AEM Cloud Service < 2023.1.0
    Affected if Your version falls within either of these vulnerable ranges

You are affected if your AEM installation (on-premise) is below version 6.5.16.0 or your AEM Cloud Service is below version 2023.1.0.

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.16.0 / 2023.1.0 or later
Fixed in 6.5.16.02023.1.0
Interim mitigation

Apply Adobe's security update (version 6.5.16.0 or later) or install the corresponding security patch to remediate the open redirect vulnerability.

Recommended fix High confidence

Experience Manager 6.5.16.0 (on-premise) or 2023.1.0 (Cloud Service)

  1. Upgrade Adobe Experience Manager on-premise installation to version 6.5.16.0 or later
  2. For Adobe Experience Manager Cloud Service, ensure the environment is updated to version 2023.1.0 or later
  3. Verify after upgrade that the open redirect vulnerability is no longer present by testing URL redirection functionality

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-2023-22263 — 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-22263 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