{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-7562 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-7562 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7562 is a medium-severity vulnerability in phkcorp2005 WP-Redirection, published on 12 May 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-7562 and fix it if it is affected.\n\nWhat it is: CVE-2026-7562 is a medium-severity vulnerability in phkcorp2005 WP-Redirection, published on 12 May 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-7562 in the wild and no public exploit code.\n\nAffected product: phkcorp2005 WP-Redirection. 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-7562/ (Markdown: https://insights.sbomify.com/CVE-2026-7562/index.md)","id":"CVE-2026-7562","markdown":"https://insights.sbomify.com/CVE-2026-7562/index.md","name":"CVE-2026-7562","record":{"aliases":["GHSA-99c9-fq53-p5w8"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick administrators into modifying or deleting URL redirection rules via CSRF due to missing nonce verification in the WP-Redirection 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 WP-Redirection plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.0.3. This is due to the absence of a nonce field in the admin settings form and the lack of any nonce verification (via check_admin_referer() or wp_verify_nonce()) in the displayWPRedirectionManagementPage() function before processing POST requests that add, edit, or delete URL redirection rules. This makes it possible for unauthenticated attackers to trick a logged-in administrator into clicking a crafted link, causing the attacker to create, modify, or delete redirection records in the plugin's database table without the administrator's consent.","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":"WP-Redirection \u003c= 1.0.3 - Cross-Site Request Forgery to Settings Update","id":"CVE-2026-7562","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Missing authorization in Classified Listing – AI-Powered Classified ads \u0026 Business Directory Plugin","id":"CVE-2026-7563"},"packages":[],"prev":{"headline":"Tm – WordPress Redirection \u003c= 1.2 - Cross-Site Request Forgery to Stored Cross-Site Scripting","id":"CVE-2026-7561"},"products":["WP-Redirection"],"published":"2026-05-12","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-05-12","vendors":["phkcorp2005"]},"summary":"Attackers can trick administrators into modifying or deleting URL redirection rules via CSRF due to missing nonce verification in the WP-Redirection plugin.","url":"https://insights.sbomify.com/CVE-2026-7562/"}