WordPress plugin · Updated daily · Source: Wordfence Intelligence

Access Governance for WordPress (aka AAM) vulnerabilities: affected versions and fixes

Access Governance for WordPress (aka AAM) has 100,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Access Governance for WordPress (aka AAM) at a glance

  • 12 publicly disclosed vulnerabilities, 4 of them rated High or Critical. The most recent was disclosed on May 14, 2026.
  • Ranked #397 by popularity on WordPress.org (100,000+ active installs).
  • The latest version is 8.0.2 (released Oct 19, 2026). The most recent security fix shipped in 7.1.1.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Access Governance for WordPress (aka AAM) version

Enter the Access Governance for WordPress (aka AAM) version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Access Governance for WordPress (aka AAM)”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Access Governance for WordPress (aka AAM)”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (8.0.2). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Access Governance for WordPress (aka AAM) vulnerabilities

  • Advanced Access Manager – Access Governance for WordPress <= 7.1.0 - Missing Authorization

    Missing authorization · CVE-2026-42674

    Affected versions: ≤ 7.1.0

    Fixed in: 7.1.1

    Severity: Medium 5.3 · Disclosed May 14, 2026

  • Advanced Access Manager <= 6.9.20 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-29127

    Affected versions: ≤ 6.9.20

    Fixed in: 6.9.21

    Severity: Medium 6.1 · Disclosed Mar 20, 2024

  • Advanced Access Manager <= 6.9.20 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-29124

    Affected versions: ≤ 6.9.20

    Fixed in: 6.9.21

    Severity: Medium 5.5 · Disclosed Mar 16, 2024

  • Advanced Access Manager <= 6.9.18 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

    Cross-site scripting (XSS) · CVE-2023-51674

    Affected versions: ≤ 6.9.18

    Fixed in: 6.9.19

    Severity: Medium 6.4 · Disclosed Dec 27, 2023

  • Advanced Access Manager <= 6.9.18 - Authenticated (Author+) Open Redirect

    Open redirect · CVE-2023-51675

    Affected versions: ≤ 6.9.18

    Fixed in: 6.9.19

    Severity: Medium 4.3 · Disclosed Dec 27, 2023

  • Advanced Access Manager <= 6.9.15 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-50881

    Affected versions: ≤ 6.9.15

    Fixed in: 6.9.16

    Severity: Medium 6.4 · Disclosed Dec 26, 2023

  • Advanced Access Manager <= 6.7.9 - Admin+ Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2021-24830

    Affected versions: < 6.8.0

    Fixed in: 6.8.0

    Severity: Medium 4.8 · Disclosed Oct 19, 2021

  • Advanced Access Manager <= 6.6.1 - Authenticated Information Disclosure

    Information disclosure · CVE-2020-35934

    Affected versions: ≤ 6.6.1

    Fixed in: 6.6.2

    Severity: Medium 4.3 · Disclosed Aug 20, 2020

  • Advanced Access Manager <= 6.6.1 - Authenticated Authorization Bypass and Privilege Escalation

    Privilege escalation · CVE-2020-35935

    Affected versions: ≤ 6.6.1

    Fixed in: 6.6.2

    Severity: High 7.5 · Disclosed Aug 14, 2020

  • Advanced Access Manager <= 5.9.8.1 - Unauthenticated Arbitrary File Read

    Arbitrary file read or deletion · CVE-2019-25213

    Affected versions: < 5.9.9

    Fixed in: 5.9.9

    Severity: Critical 9.8 · Disclosed Sep 9, 2019

  • Advanced Access Manager <= 3.2.1 - Unrestricted AJAX Actions allowing Privilege Escalation

    Privilege escalation

    Affected versions: < 3.2.2

    Fixed in: 3.2.2

    Severity: High 8.8 · Disclosed Jun 21, 2016

  • Advanced Access Manager <= 2.8.2 - Arbitrary File Overwrite

    Other weakness · CVE-2014-6059

    Affected versions: < 2.8.3

    Fixed in: 2.8.3

    Severity: High 7.2 · Disclosed Aug 20, 2014

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: May 14, 2026.

Most common weaknesses in Access Governance for WordPress (aka AAM)

Cross-site scripting (XSS)

5 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Privilege escalation

2 issues

A user with a low-level account, such as a subscriber or customer, can give themselves administrator rights.

Missing authorization

1 issue

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Frequently asked questions

Is Access Governance for WordPress (aka AAM) safe to use?

Access Governance for WordPress (aka AAM) is a well-known plugin with 100,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (8.0.2) and turn on automatic updates.

How do I find which version of Access Governance for WordPress (aka AAM) my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesAccess Governance for WordPress (aka AAM) on WordPress.org