{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-24636 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-24636 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24636 is a high-severity vulnerability in Unknown Print My Blog – Print, PDF, \u0026 eBook Converter WordPress Plugin, published on 20 Sep 2021. 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-2021-24636 and fix it if it is affected.\n\nWhat it is: CVE-2021-24636 is a high-severity vulnerability in Unknown Print My Blog – Print, PDF, \u0026 eBook Converter WordPress Plugin, published on 20 Sep 2021. 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-2021-24636 in the wild and no public exploit code.\n\nAffected product: Unknown Print My Blog – Print, PDF, \u0026 eBook Converter WordPress Plugin. 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-2021-24636/ (Markdown: https://insights.sbomify.com/CVE-2021-24636/index.md)","id":"CVE-2021-24636","markdown":"https://insights.sbomify.com/CVE-2021-24636/index.md","name":"CVE-2021-24636","record":{"aliases":["GHSA-587q-w3p6-m55g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick administrators into deactivating the Print My Blog plugin and deleting its data via a malicious link due to missing CSRF checks.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"print_my_blog","vendor":"print_my_blog_project"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Print My Blog WordPress Plugin before 3.4.2 does not enforce nonce (CSRF) checks, which allows attackers to make logged in administrators deactivate the Print My Blog plugin and delete all saved data for that plugin by tricking them to open a malicious 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":"Print My Blog \u003c 3.4.2 - Plugin Deactivation via CSRF","id":"CVE-2021-24636","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Fonts Plugin \u003c 3.0.3 - Contributor+ Stored Cross-Site Scripting","id":"CVE-2021-24637"},"packages":[],"prev":{"headline":"Visual Link Preview \u003c 2.2.3 - Unauthorised AJAX Calls","id":"CVE-2021-24635"},"products":["Print My Blog – Print, PDF, \u0026 eBook Converter WordPress Plugin"],"published":"2021-09-20","related":[{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2019-11565","kev_date_added":null,"published":"2019-04-27"},{"cvss_score":5.9,"headline":"WordPress Print My Blog plugin \u003c= 3.27.0 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-37271","kev_date_added":null,"published":"2024-07-22"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"Attackers can trick administrators into deactivating the Print My Blog plugin and deleting its data via a malicious link due to missing CSRF checks.","url":"https://insights.sbomify.com/CVE-2021-24636/"}