{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-8104 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-8104 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8104 is a medium-severity vulnerability in sminozzi Memory Usage, Memory Limit, PHP and Server Memory Health Check and Provide Suggestions, published on 27 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-8104 and fix it if it is affected.\n\nWhat it is: CVE-2025-8104 is a medium-severity vulnerability in sminozzi Memory Usage, Memory Limit, PHP and Server Memory Health Check and Provide Suggestions, published on 27 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-8104 in the wild and no public exploit code.\n\nAffected product: sminozzi Memory Usage, Memory Limit, PHP and Server Memory Health Check and Provide Suggestions. 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-2025-8104/ (Markdown: https://insights.sbomify.com/CVE-2025-8104/index.md)","id":"CVE-2025-8104","markdown":"https://insights.sbomify.com/CVE-2025-8104/index.md","name":"CVE-2025-8104","record":{"aliases":["GHSA-4fhw-xxqc-jv7q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick administrators into installing whitelisted plugins via CSRF due to missing nonce validation in the Memory Usage plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Memory Usage plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.98. This is due to missing nonce validation in the wpmemory_install_plugin() function. This makes it possible for unauthenticated attackers to silently install one of the several whitelisted plugins via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory Usage \u003c= 3.98 - Cross-Site Request Forgery to Limited Plugin Installation via wpmemory_install_plugin Function","id":"CVE-2025-8104","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Soledad \u003c= 8.6.7 - Unauthenticated Arbitrary Shortcode Execution","id":"CVE-2025-8105"},"packages":[],"prev":{"headline":"Cross-site request forgery in WPeMatico RSS Feed Fetcher","id":"CVE-2025-8103"},"products":["Memory Usage, Memory Limit, PHP and Server Memory Health Check and Provide Suggestions"],"published":"2025-07-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["sminozzi"]},"summary":"Attackers can trick administrators into installing whitelisted plugins via CSRF due to missing nonce validation in the Memory Usage plugin.","url":"https://insights.sbomify.com/CVE-2025-8104/"}