{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-32568 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-32568 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-32568 is a high-severity cross-site scripting vulnerability in Melapress WP 2FA, published on 18 Apr 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-2024-32568 and fix it if it is affected.\n\nWhat it is: CVE-2024-32568 is a high-severity cross-site scripting vulnerability in Melapress WP 2FA, published on 18 Apr 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-2024-32568 in the wild and no public exploit code.\n\nAffected product: Melapress WP 2FA. 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-2024-32568/ (Markdown: https://insights.sbomify.com/CVE-2024-32568/index.md)","id":"CVE-2024-32568","markdown":"https://insights.sbomify.com/CVE-2024-32568/index.md","name":"CVE-2024-32568","record":{"aliases":["GHSA-w37p-9fqc-g3gp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can inject malicious scripts into the WP 2FA plugin, potentially stealing user sessions or executing code in victim browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"wp_2fa","vendor":"melapress"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Melapress WP 2FA wp-2fa.This issue affects WP 2FA: from n/a through \u003c= 2.6.2.","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 WP 2FA plugin \u003c= 2.6.2 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-32568","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Ditty plugin \u003c= 3.1.31 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-32569"},"packages":[],"prev":{"headline":"WordPress DirectoryPress plugin \u003c= 3.6.7 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-32567"},"products":["WP 2FA"],"published":"2024-04-18","related":[{"cvss_score":5.3,"headline":"WordPress WP 2FA plugin \u003c= 2.6.3 - Sensitive Data Exposure via Log File vulnerability","id":"CVE-2022-44587","kev_date_added":null,"published":"2024-06-21"},{"cvss_score":5.3,"headline":"WordPress WP2FA plugin \u003c= 2.2.0 - Broken Authentication vulnerability","id":"CVE-2022-44595","kev_date_added":null,"published":"2024-03-21"},{"cvss_score":4.3,"headline":"WP 2FA – Two-factor authentication for WordPress \u003c= 2.5.0 - Cross-Site Request Forgery","id":"CVE-2023-6520","kev_date_added":null,"published":"2024-01-11"}],"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":["Melapress"]},"summary":"Attackers can inject malicious scripts into the WP 2FA plugin, potentially stealing user sessions or executing code in victim browsers.","url":"https://insights.sbomify.com/CVE-2024-32568/"}