dbcve.org
Advanced Access ManagerWordPress extension · Vasyltech

CVE-2023-51674

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-01
Fix available
A fix is available. Upgrade to after 6.9.18 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in AAM Advanced Access Manager – Restricted Content, Users & Roles, Enhanced Security and More allows Stored XSS.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 · moderate confidence

This is a Stored XSS vulnerability in the Advanced Access Manager WordPress plugin. Attackers can inject malicious JavaScript code into the plugin's fields or parameters, which gets stored in the database and executed when administrators or other users access affected pages in the WordPress admin dashboard.

MitigationUpdate the Advanced Access Manager plugin to version 6.9.19 or later, which should contain the fix for this vulnerability. Additionally, ensure all user inputs are properly sanitized using WordPress sanitization functions and outputs are encoded appropriately.

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.18

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 installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate 'Advanced Access Manager' (or 'AAM'), and view the version number under the plugin name. Alternatively, check the main plugin file (e.g., /wp-content/plugins/advanced-access-manager/aam.php) for the 'Version' header in the file comment.
    Affected if Version number is 6.9.18 or lower.
  2. Verify plugin is active
    In WordPress admin > Plugins, confirm the Advanced Access Manager plugin shows as 'Active'. If deactivated, the stored XSS cannot be triggered.
    Affected if Plugin is active and accessible to authenticated users.
  3. Identify plugin settings pages
    Access the Advanced Access Manager plugin in the WordPress admin sidebar. Look for any settings pages, user role configurations, capability assignments, or menu/URL access settings where user input is accepted.
    Affected if Any plugin settings page accepts user input that gets saved to the database.
  4. Inspect database for suspicious stored content
    Query the WordPress database (via phpMyAdmin or wp CLI) for any stored XSS payloads in plugin-related tables. Look for common XSS patterns such as '<script', 'javascript:', 'onerror=', 'onload=' within the wp_options table or any aam-related tables.
    Affected if Any records contain unsanitized JavaScript or HTML tags in plugin-related fields.
  5. Review user roles and capabilities settings
    In the AAM plugin panel, check the Users, Roles, and Capabilities sections for any unexpected or unauthorized modifications, particularly in fields that accept text input.
    Affected if Unknown or malicious entries exist in role/capability configuration fields.

A user is affected if the Advanced Access Manager plugin version is 6.9.18 or lower, the plugin is active, and any plugin settings fields accept user input that could be stored with unsanitized content.

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 6.9.18
Interim mitigation

Update the Advanced Access Manager plugin to version 6.9.19 or later, which should contain the fix for this vulnerability. Additionally, ensure all user inputs are properly sanitized using WordPress sanitization functions and outputs are encoded appropriately.

Recommended fix Moderate confidence

Latest version of Advanced Access Manager after 6.9.18 (verify the fixed version on wordpress.org or the developer's site)

  1. Check the WordPress plugin repository or the official AAM website for the latest version of Advanced Access Manager
  2. Update the plugin to the latest available version that addresses this vulnerability
  3. After updating, verify the fix by testing the affected functionality that previously allowed stored XSS
  4. Ensure all WordPress core and other plugins are also kept up to date
Caveat Review plugin changelog for any breaking changes before upgrading in production environments

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

Fix this in Advanced Access Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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