{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-0592 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-0592 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-0592 is a medium-severity vulnerability in barrykooij Related Posts for WordPress, published on 13 Mar 2024. 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-2024-0592 and fix it if it is affected.\n\nWhat it is: CVE-2024-0592 is a medium-severity vulnerability in barrykooij Related Posts for WordPress, published on 13 Mar 2024. 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-2024-0592 in the wild and no public exploit code.\n\nAffected product: barrykooij Related Posts for WordPress. 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-2024-0592/ (Markdown: https://insights.sbomify.com/CVE-2024-0592/index.md)","id":"CVE-2024-0592","markdown":"https://insights.sbomify.com/CVE-2024-0592/index.md","name":"CVE-2024-0592","record":{"aliases":["GHSA-hh53-w78f-76fc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick admins into adding related posts, allowing unauthorized access to draft and password-protected content via CSRF.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"related_posts","vendor":"never5"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Related Posts for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.1. This is due to missing or incorrect nonce validation on the handle_create_link() function. This makes it possible for unauthenticated attackers to add related posts to other posts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This ultimately makes it possible for attackers to view draft and password protected posts.","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":"Related Posts for WordPress \u003c= 2.2.1 - Cross-Site Request Forgery","id":"CVE-2024-0592","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Simple Job Board \u003c= 2.10.8 - Missing Authorization to Unauthenticated Information Disclosure","id":"CVE-2024-0593"},"packages":[],"prev":{"headline":"wpDataTables – WordPress Data Table, Dynamic Tables \u0026 Table Charts Plugin \u003c= 3.4.2.2 - Reflected Cross-Site Scripting.","id":"CVE-2024-0591"},"products":["Related Posts for WordPress"],"published":"2024-03-13","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2015-9361","kev_date_added":null,"published":"2019-08-28"},{"cvss_score":5.5,"headline":"Cross-site Scripting (XSS) - Stored in barrykooij/related-posts-for-wp","id":"CVE-2022-3506","kev_date_added":null,"published":"2022-10-14"},{"cvss_score":5.4,"headline":"Related Posts for WordPress \u003c 2.0.4 - Authenticated Reflected Cross-Site Scripting (XSS)","id":"CVE-2021-24180","kev_date_added":null,"published":"2021-04-05"},{"cvss_score":4.8,"headline":"Related Posts for WordPress \u003c= 2.0.4 - Authenticated Stored XSS \u0026 XFS","id":"CVE-2021-24482","kev_date_added":null,"published":"2021-07-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":["barrykooij"]},"summary":"Attackers can trick admins into adding related posts, allowing unauthorized access to draft and password-protected content via CSRF.","url":"https://insights.sbomify.com/CVE-2024-0592/"}