{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-68547 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-68547 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68547 is a high-severity missing authorization vulnerability in wpweb Follow My Blog Post, published on 5 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68547 and fix it if it is affected.\n\nWhat it is: CVE-2025-68547 is a high-severity missing authorization vulnerability in wpweb Follow My Blog Post, published on 5 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68547 in the wild and no public exploit code.\n\nAffected product: wpweb Follow My Blog Post. 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-2025-68547/ (Markdown: https://insights.sbomify.com/CVE-2025-68547/index.md)","id":"CVE-2025-68547","markdown":"https://insights.sbomify.com/CVE-2025-68547/index.md","name":"CVE-2025-68547","record":{"aliases":["GHSA-7q6w-g6fh-h25h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can arbitrarily delete content in the Follow My Blog Post WordPress plugin due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"follow_my_blog_post","vendor":"wpwebelite"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Missing Authorization vulnerability in wpweb Follow My Blog Post follow-my-blog-post allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Follow My Blog Post: from n/a through \u003c= 2.4.0.","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":"WordPress Follow My Blog Post plugin \u003c= 2.4.0 - Arbitrary Content Deletion vulnerability","id":"CVE-2025-68547","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Responsive Posts Carousel Pro plugin \u003c= 15.2 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2025-68548"},"packages":[],"prev":{"headline":"WordPress Nika theme \u003c= 1.2.14 - Local File Inclusion vulnerability","id":"CVE-2025-68546"},"products":["Follow My Blog Post"],"published":"2026-01-05","related":[{"cvss_score":7.5,"headline":"WordPress Follow My Blog Post plugin \u003c= 2.3.9 - Sensitive Data Exposure vulnerability","id":"CVE-2025-64258","kev_date_added":null,"published":"2025-12-18"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["wpweb"]},"summary":"An attacker can arbitrarily delete content in the Follow My Blog Post WordPress plugin due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2025-68547/"}