{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4131 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4131 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4131 is a medium-severity vulnerability in sphex1987 WP Responsive Popup + Optin, published on 22 Apr 2026. 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-2026-4131 and fix it if it is affected.\n\nWhat it is: CVE-2026-4131 is a medium-severity vulnerability in sphex1987 WP Responsive Popup + Optin, published on 22 Apr 2026. 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-2026-4131 in the wild and no public exploit code.\n\nAffected product: sphex1987 WP Responsive Popup + Optin. 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-4131/ (Markdown: https://insights.sbomify.com/CVE-2026-4131/index.md)","id":"CVE-2026-4131","markdown":"https://insights.sbomify.com/CVE-2026-4131/index.md","name":"CVE-2026-4131","record":{"aliases":["GHSA-mjqc-rj22-4rf2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick admins into updating plugin settings, enabling stored XSS via image URL parameter due to missing CSRF protection.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP Responsive Popup + Optin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.4. This is due to the settings form on the admin page (wpo_admin_page.php) lacking nonce generation (wp_nonce_field) and verification (wp_verify_nonce/check_admin_referer). This makes it possible for unauthenticated attackers to update all plugin settings including the 'wpo_image_url' parameter via a forged request, granted they can trick a site administrator into performing an action such as clicking 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":"Cross-site request forgery in WP Responsive Popup + Optin","id":"CVE-2026-4131","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":11,"next":{"headline":"Path traversal in HTTP Headers","id":"CVE-2026-4132"},"packages":[],"prev":{"headline":"Storage of Sensitive Information in Cleartext in NI SystemLink","id":"CVE-2026-4130"},"products":["WP Responsive Popup + Optin"],"published":"2026-04-22","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-22","vendors":["sphex1987"]},"summary":"Attackers can trick admins into updating plugin settings, enabling stored XSS via image URL parameter due to missing CSRF protection.","url":"https://insights.sbomify.com/CVE-2026-4131/"}