{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-1648 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-1648 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-1648 is a high-severity server-side request forgery vulnerability in qrolic Performance Monitor, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-1648 and fix it if it is affected.\n\nWhat it is: CVE-2026-1648 is a high-severity server-side request forgery vulnerability in qrolic Performance Monitor, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-1648 in the wild and no public exploit code.\n\nAffected product: qrolic Performance Monitor. 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-2026-1648/ (Markdown: https://insights.sbomify.com/CVE-2026-1648/index.md)","id":"CVE-2026-1648","markdown":"https://insights.sbomify.com/CVE-2026-1648/index.md","name":"CVE-2026-1648","record":{"aliases":["GHSA-4vr9-8jj4-gfwv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can exploit SSRF in the Performance Monitor plugin to access internal services and potentially achieve remote code execution.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The Performance Monitor plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.0.6. This is due to insufficient validation of the 'url' parameter in the '/wp-json/performance-monitor/v1/curl_data' REST API endpoint. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations, including internal services, via the Gopher protocol and other dangerous protocols. This can be exploited to achieve Remote Code Execution by chaining with services like Redis.","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":"Performance Monitor \u003c= 1.0.6 - Unauthenticated Server-Side Request Forgery via 'url' Parameter","id":"CVE-2026-1648","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Community Events \u003c= 1.5.7 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'ce_venue_name' Parameter","id":"CVE-2026-1649"},"packages":[],"prev":{"headline":"Comment Genius \u003c= 1.2.5 - Reflected Cross-Site Scripting via $_SERVER['PHP_SELF']","id":"CVE-2026-1647"},"products":["Performance Monitor"],"published":"2026-03-21","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["qrolic"]},"summary":"Unauthenticated attackers can exploit SSRF in the Performance Monitor plugin to access internal services and potentially achieve remote code execution.","url":"https://insights.sbomify.com/CVE-2026-1648/"}