{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4552 exists.","fix":"No fix has been published for CVE-2022-4552 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4552 is a medium-severity vulnerability in Unknown FL3R FeelBox, published on 30 Jan 2023. 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-4552 and fix it if it is affected.\n\nWhat it is: CVE-2022-4552 is a medium-severity vulnerability in Unknown FL3R FeelBox, published on 30 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4552 exists.\n\nAffected product: Unknown FL3R FeelBox. 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-4552/ (Markdown: https://insights.sbomify.com/CVE-2022-4552/index.md)","id":"CVE-2022-4552","markdown":"https://insights.sbomify.com/CVE-2022-4552/index.md","name":"CVE-2022-4552","record":{"aliases":["GHSA-p5qx-gv99-2q5m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can force logged-in admins to update settings with stored XSS payloads via CSRF, leading to code execution.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"fl3r_feelbox","vendor":"armandofiore"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The FL3R FeelBox WordPress plugin through 8.1 does not have CSRF check when updating its settings, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack","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":"FL3R FeelBox \u003c= 8.1 - Settings Update via CSRF to Stored XSS","id":"CVE-2022-4552","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"FL3R FeelBox \u003c= 8.1 - Moods Reset via CSRF","id":"CVE-2022-4553"},"packages":[],"prev":{"headline":"Rich Table of Contents \u003c 1.3.9 - Contributor+ Stored XSS","id":"CVE-2022-4551"},"products":["FL3R FeelBox"],"published":"2023-01-30","related":[{"cvss_score":9.8,"headline":"FL3R FeelBox \u003c= 8.1 - Unauthenticated SQLi","id":"CVE-2022-4445","kev_date_added":null,"published":"2023-02-13"},{"cvss_score":4.3,"headline":"FL3R FeelBox \u003c= 8.1 - Moods Reset via CSRF","id":"CVE-2022-4553","kev_date_added":null,"published":"2023-01-30"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-27","vendors":["Unknown"]},"summary":"Attackers can force logged-in admins to update settings with stored XSS payloads via CSRF, leading to code execution.","url":"https://insights.sbomify.com/CVE-2022-4552/"}