{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4680 exists.","fix":"No fix has been published for CVE-2022-4680 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4680 is a high-severity unsafe deserialization vulnerability in Unknown Revive Old Posts, published on 30 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-4680 and fix it if it is affected.\n\nWhat it is: CVE-2022-4680 is a high-severity unsafe deserialization vulnerability in Unknown Revive Old Posts, published on 30 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4680 exists.\n\nAffected product: Unknown Revive Old Posts. 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-2022-4680/ (Markdown: https://insights.sbomify.com/CVE-2022-4680/index.md)","id":"CVE-2022-4680","markdown":"https://insights.sbomify.com/CVE-2022-4680/index.md","name":"CVE-2022-4680","record":{"aliases":["GHSA-pqm2-5wmp-22wm"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Admins can trigger PHP object injection via unsafe deserialization in settings, potentially leading to code execution if gadgets exist.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"revive_old_posts","vendor":"revive"}],"cvss":{"score":7.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"The Revive Old Posts WordPress plugin before 9.0.11 unserializes user input provided via the settings, which could allow high privilege users such as admin to perform PHP Object Injection when a suitable gadget is present.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Revive Old Posts – Social Media Auto Post and Scheduling Plugin \u003c 9.0.11 - PHP Object Injection","id":"CVE-2022-4680","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Hide My WP \u003c 6.2.9 - Unauthenticated SQLi","id":"CVE-2022-4681"},"packages":[],"prev":{"headline":"Wufoo Shortcode \u003c 1.52 - Contributor+ Stored XSS via Shortcode","id":"CVE-2022-4679"},"products":["Revive Old Posts"],"published":"2023-01-30","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-27","vendors":["Unknown"]},"summary":"Admins can trigger PHP object injection via unsafe deserialization in settings, potentially leading to code execution if gadgets exist.","url":"https://insights.sbomify.com/CVE-2022-4680/"}