dbcve.org
Advanced Access ManagerWordPress extension · Vasyltech

CVE-2023-51675

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-29
Fix available
A fix is available. Upgrade to 6.9.19 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
URL Redirection to Untrusted Site ('Open Redirect') vulnerability in AAM Advanced Access Manager – Restricted Content, Users & Roles, Enhanced Security and More.This issue affects Advanced Access Manager – Restricted Content, Users & Roles, Enhanced Security and More: from n/a through 6.9.18.

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

Open redirect vulnerability in the AAM WordPress plugin allows attackers to craft malicious URLs that redirect users to untrusted external sites. The vulnerability exists in the redirect handling logic, likely through a URL parameter that isn't properly validated to ensure it remains within the expected domain or uses relative paths.

MitigationUpdate AAM plugin to version 6.9.19 or later which contains the fix. If immediate update isn't possible, review and restrict any redirect-related parameters in the plugin's configuration to prevent user-controlled redirect destinations.

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
Advanced Access ManagerWordPress extension
Affected:< 6.9.19

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 AAM plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Advanced Access Manager' (or AAM). The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag, typically in wp-content/plugins/advanced-access-manager/main.php
    Affected if Version is lower than 6.9.19 (e.g., 6.9.18, 6.9.17, etc.)
  2. Identify redirect feature configuration
    Navigate to AAM plugin settings in WordPress admin (usually under Users > Access Manager or a dedicated AAM menu). Look for sections related to 'Redirect', 'Login Redirect', 'Logout Redirect', or 'Access Denied Redirect'
    Affected if Any redirect rules are configured that accept URL parameters or allow user-specified destinations
  3. Inspect redirect URL parameters
    If redirect configurations exist, examine the stored redirect URLs. Check whether any redirect destination uses dynamic parameters (e.g., includes 'redirect_to', 'return', or similar query string variables) or allows external URLs
    Affected if Redirect destinations accept untrusted input or pass through URL parameters without domain validation
  4. Test for unvalidated redirect parameter
    If your site has AAM functionality accessible, attempt to access a known AAM-handled URL (such as a login page or restricted content) with a test parameter like '?redirect=http://example.com' or '?return=https://evil.com' to observe if arbitrary external URLs are accepted
    Affected if The plugin accepts and follows redirect destinations to external domains without validation

You are affected if the AAM plugin version is below 6.9.19 AND any redirect functionality is in use, since the vulnerability allows attackers to craft URLs that redirect users to untrusted external sites.

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.9.19 or later
Fixed in 6.9.19
Interim mitigation

Update AAM plugin to version 6.9.19 or later which contains the fix. If immediate update isn't possible, review and restrict any redirect-related parameters in the plugin's configuration to prevent user-controlled redirect destinations.

Recommended fix High confidence

6.9.19

  1. 1. Update the Advanced Access Manager plugin to version 6.9.19 or later through the WordPress admin dashboard (Plugins > Updates)
  2. 2. Alternatively, manually upload the updated plugin via Plugins > Add New > Upload Plugin
  3. 3. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins

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

Fix this in Advanced Access 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-51675 — 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-2023-51675 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