{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6294 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6294 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6294 is a medium-severity vulnerability in byybora Google PageRank Display, 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-6294 and fix it if it is affected.\n\nWhat it is: CVE-2026-6294 is a medium-severity vulnerability in byybora Google PageRank Display, 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-6294 in the wild and no public exploit code.\n\nAffected product: byybora Google PageRank Display. 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-6294/ (Markdown: https://insights.sbomify.com/CVE-2026-6294/index.md)","id":"CVE-2026-6294","markdown":"https://insights.sbomify.com/CVE-2026-6294/index.md","name":"CVE-2026-6294","record":{"aliases":["GHSA-8w4w-mfg4-cvw8"],"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":"Unauthenticated attackers can trick administrators into changing plugin settings via CSRF due to missing nonce validation in the Google PageRank Display WordPress 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 Google PageRank Display plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to and including 1.4. This is due to missing nonce validation in the gpdisplay_option() function, which handles the plugin settings page. The settings form does not include a wp_nonce_field(), and the form handler does not call check_admin_referer() or wp_verify_nonce() before processing the POST request. This makes it possible for unauthenticated attackers to trick a logged-in administrator into submitting a crafted request that changes the plugin's settings (stored via update_option()), such as the display style used to render the PageRank badge.","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":"Google PageRank Display \u003c= 1.4 - Cross-Site Request Forgery to Settings Update via Settings Page","id":"CVE-2026-6294","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"WP Optimizer \u003c= 2.5.0 - Authenticated (Administrator+) SQL Injection via 's' Parameter","id":"CVE-2026-6295"},"packages":[],"prev":{"headline":"Cross-site request forgery in Inquiry form to posts or pages","id":"CVE-2026-6293"},"products":["Google PageRank Display"],"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":["byybora"]},"summary":"Unauthenticated attackers can trick administrators into changing plugin settings via CSRF due to missing nonce validation in the Google PageRank Display WordPress plugin.","url":"https://insights.sbomify.com/CVE-2026-6294/"}