{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-1845 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-1845 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-1845 is a medium-severity vulnerability in Unknown WP Post Styling, published on 27 Jun 2022. 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-2022-1845 and fix it if it is affected.\n\nWhat it is: CVE-2022-1845 is a medium-severity vulnerability in Unknown WP Post Styling, published on 27 Jun 2022. 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-2022-1845 in the wild and no public exploit code.\n\nAffected product: Unknown WP Post Styling. 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-1845/ (Markdown: https://insights.sbomify.com/CVE-2022-1845/index.md)","id":"CVE-2022-1845","markdown":"https://insights.sbomify.com/CVE-2022-1845/index.md","name":"CVE-2022-1845","record":{"aliases":["GHSA-jpvc-cfc6-xwc3"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick logged-in admins into performing unauthorized actions like deleting data or changing settings in the WP Post Styling plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_post_styling","vendor":"wp_post_styling_project"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP Post Styling WordPress plugin before 1.3.1 does not have CSRF checks in various actions, which could allow attackers to make a logged in admin delete plugin's data, update the settings, add new entries and more via CSRF attacks","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":"WP Post Styling \u003c 1.3.1 - Multiple CSRF","id":"CVE-2022-1845","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Tiny Contact Form \u003c= 0.7 - Arbitrary Settings Update via CSRF","id":"CVE-2022-1846"},"packages":[],"prev":{"headline":"WP Sentry \u003c= 1.0 - Arbitrary Settings Update to Stored XSS via CSRF","id":"CVE-2022-1844"},"products":["WP Post Styling"],"published":"2022-06-27","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"Attackers can trick logged-in admins into performing unauthorized actions like deleting data or changing settings in the WP Post Styling plugin.","url":"https://insights.sbomify.com/CVE-2022-1845/"}