{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-51531 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-51531 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-51531 is a medium-severity vulnerability in Thrive Automator, published on 29 Feb 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-2023-51531 and fix it if it is affected.\n\nWhat it is: CVE-2023-51531 is a medium-severity vulnerability in Thrive Automator, published on 29 Feb 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-2023-51531 in the wild and no public exploit code.\n\nAffected product: Thrive Automator. 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-2023-51531/ (Markdown: https://insights.sbomify.com/CVE-2023-51531/index.md)","id":"CVE-2023-51531","markdown":"https://insights.sbomify.com/CVE-2023-51531/index.md","name":"CVE-2023-51531","record":{"aliases":["GHSA-pp5p-pf9f-v3q8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick authenticated users into performing unwanted actions in the Thrive Automator WordPress plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"thrive_automator","vendor":"thrivethemes"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) vulnerability in Thrive Themes Thrive Automator.This issue affects Thrive Automator: from n/a through 1.17.","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 Thrive Automator Plugin \u003c= 1.17 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-51531","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Icegram Plugin \u003c= 3.1.19 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-51532"},"packages":[],"prev":{"headline":"WordPress GS Logo Slider Plugin \u003c= 3.5.1 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-51530"},"products":["Thrive Automator"],"published":"2024-02-29","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":"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-28","vendors":["Thrive Themes"]},"summary":"Attackers can trick authenticated users into performing unwanted actions in the Thrive Automator WordPress plugin.","url":"https://insights.sbomify.com/CVE-2023-51531/"}