dbcve.org
Advanced Access ManagerWordPress extension · Vasyltech

CVE-2023-50881

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-29
Fix available
A fix is available. Upgrade to after 6.9.15 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.15.

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 Cross-site Scripting (XSS) vulnerability in the AAM (Advanced Access Manager) WordPress plugin. The plugin fails to properly sanitize user-supplied input, allowing malicious JavaScript code to be stored in the database and executed when administrators or other users view affected pages in the WordPress admin dashboard.

MitigationUpdate the AAM plugin to the latest version beyond 6.9.15 which contains proper input sanitization. Before updating, create a full site backup and test the update on a staging environment to ensure compatibility with other plugins and themes.

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

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
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate 'Advanced Access Manager' (AAM) in the list and read the version number displayed below the plugin name.
    Affected if The displayed version is 6.9.15 or lower (for example, 6.9.14, 6.9.10, etc.)
  2. Check plugin version via file system
    If admin access is unavailable, access the WordPress file system via FTP or file manager. Navigate to /wp-content/plugins/advanced-access-manager/ and open the readme.txt file. Locate the version number in the header section.
    Affected if The version listed in readme.txt is 6.9.15 or lower
  3. Inspect database for stored XSS in AAM options
    Access the WordPress database via phpMyAdmin or command line. Query the wp_options table (or custom prefix) for AAM-related settings. Look for option_name values containing 'aam' or 'advanced_access_manager'. Examine the option_value column for any <script> tags, javascript: URLs, or onload/onerror event handlers.
    Affected if Any option_value contains suspicious JavaScript code such as <script> tags, event handlers like onerror/onload, or javascript: protocol URIs
  4. Review AAM capability settings for injected scripts
    In the WordPress admin, go to AAM > Capabilities (or relevant AAM menu). Inspect any saved roles, capabilities, or access settings. Check for unexpected HTML or script content in text fields that accept user input.
    Affected if Any saved capability names, role labels, or setting values contain raw HTML or JavaScript code

You are affected if the installed AAM plugin version is 6.9.15 or lower, or if the database contains any suspicious script injections in AAM-related options.

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.

From vendor data
Upgrade available Upgrade to a release after 6.9.15
Interim mitigation

Update the AAM plugin to the latest version beyond 6.9.15 which contains proper input sanitization. Before updating, create a full site backup and test the update on a staging environment to ensure compatibility with other plugins and themes.

Fix this in Advanced Access Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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