CVE-2019-25213 is an unauthenticated arbitrary file read in the Advanced Access Manager WordPress plugin up to and including 5.9.8.1, scored 9.8. It abuses the aam-media parameter. Update the plugin to the latest release and confirm the exact fixed version in the changelog.
What's affected
- Product: Advanced Access Manager, a WordPress access control plugin by VasylTech.
- Affected: versions up to and including 5.9.8.1, per the NVD record.
- Fixed: the record does not name a fixed version, and the Wordfence and WordPress changeset pages did not load for this post. Check the plugin changelog or Wordfence entry.
- Severity: 9.8 Critical (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H).
- Weakness: CWE-22, path traversal, through insufficient validation on the aam-media parameter.
How to check if you're exposed
- In the WordPress admin, open Plugins and read the Advanced Access Manager version. Anything at or below 5.9.8.1 is in the affected range.
- With WP-CLI,
wp plugin listprints every plugin with its version, so filter the output for advanced-access-manager. - Review web server logs for requests that carry an aam-media parameter, and look for unusual values or requests from addresses you do not know.
- Check whether wp-config.php or backup files in the web root were requested, since the record names wp-config.php as a sensitive example.
What to do now
- Update Advanced Access Manager to the current release and verify the version in the plugin changelog.
- If the site was exposed on an affected version, rotate the database credentials and the WordPress secret keys and salts stored in wp-config.php.
- Remove backup archives, old configuration copies and other sensitive files from the web root.
- Add the plugin to your inventory of WordPress components so version drift is visible on a schedule.
Why it matters
The record says the plugin did not validate the aam-media parameter well enough, so an unauthenticated attacker could read any file on the server. That is the definition of path traversal, and it needs no account. The record names wp-config.php as an example of a sensitive file, which holds database credentials and keys.
Note that the vector scores integrity and availability as high even though the description speaks only of reading files. The score comes from the record as published. Whatever the number, a leaked wp-config.php is a serious incident. The KEV flag is false and the sources read did not report exploitation.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Does the fixed version exist?
The record only gives the affected range, up to and including 5.9.8.1. Newer releases fall outside that range, but confirm in the changelog.
Why rotate keys after patching?
Patching stops new reads. It does not undo reads that already happened. If the site was exposed, assume the file contents were seen.
Sources
- WordPress Trac changeset referenced by the record: The WordPress Trac changeset returned an access error for this post, and the Wordfence entry needed a script enabled browser. Facts come from the NVD record.
Last reviewed: 19 October 2026.