{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25213 exists.","fix":"No fix has been published for CVE-2019-25213 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-25213 is a critical path traversal vulnerability in vasyltech Advanced Access Manager – Access Governance for WordPress, published on 16 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-25213 and fix it if it is affected.\n\nWhat it is: CVE-2019-25213 is a critical path traversal vulnerability in vasyltech Advanced Access Manager – Access Governance for WordPress, published on 16 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25213 exists.\n\nAffected product: vasyltech Advanced Access Manager – Access Governance for WordPress. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-25213/ (Markdown: https://insights.sbomify.com/CVE-2019-25213/index.md)","id":"CVE-2019-25213","markdown":"https://insights.sbomify.com/CVE-2019-25213/index.md","name":"CVE-2019-25213","record":{"aliases":["GHSA-wx98-rpcr-jrwv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can read arbitrary files on the server, including sensitive configuration files, via insufficient validation in the Advanced Access Manager plugin.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"advanced_access_manager","vendor":"vasyltech"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The Advanced Access Manager plugin for WordPress is vulnerable to Unauthenticated Arbitrary File Read in versions up to, and including, 5.9.8.1 due to insufficient validation on the aam-media parameter. This allows unauthenticated attackers to read any file on the server, including sensitive files such as wp-config.php","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2019/CVE-2019-25213.yaml","stars":null,"title":"WordPress Advanced Access Manager - Path Traversal"}],"tier":"weaponised"},"has_fix":null,"headline":"Advanced Access Manager \u003c= 5.9.8.1 - Unauthenticated Arbitrary File Read","id":"CVE-2019-25213","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"ShopWP \u003c= 2.0.4 - Missing Authorization to Stored Cross-Site Scripting","id":"CVE-2019-25214"},"packages":[],"prev":{"headline":"video carousel slider with lightbox \u003c= 1.0.6 - Authenticated (Admin+) SQL Injection","id":"CVE-2019-25212"},"products":["Advanced Access Manager – Access Governance for WordPress"],"published":"2024-10-16","related":[{"cvss_score":7.5,"headline":"Privilege escalation in n/a","id":"CVE-2020-35935","kev_date_added":null,"published":"2021-01-01"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2014-6059","kev_date_added":null,"published":"2020-01-13"},{"cvss_score":7.1,"headline":"WordPress Advanced Access Manager plugin \u003c= 6.9.20 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-29127","kev_date_added":null,"published":"2024-03-19"},{"cvss_score":6.5,"headline":"WordPress Advanced Access Manager Plugin \u003c= 6.9.18 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-51674","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":6.5,"headline":"WordPress Advanced Access Manager Plugin \u003c= 6.9.15 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-50881","kev_date_added":null,"published":"2023-12-29"},{"cvss_score":4.8,"headline":"Advanced Access Manager \u003c 6.8.0 - Admin+ Stored Cross-Site Scripting","id":"CVE-2021-24830","kev_date_added":null,"published":"2021-11-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["vasyltech"]},"summary":"Unauthenticated attackers can read arbitrary files on the server, including sensitive configuration files, via insufficient validation in the Advanced Access Manager plugin.","url":"https://insights.sbomify.com/CVE-2019-25213/"}