{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-4536 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-4536 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4536 is a medium-severity vulnerability in youtag Two-factor authentication (formerly IP Vault), published on 31 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-4536 and fix it if it is affected.\n\nWhat it is: CVE-2022-4536 is a medium-severity vulnerability in youtag Two-factor authentication (formerly IP Vault), published on 31 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-4536 in the wild and no public exploit code.\n\nAffected product: youtag Two-factor authentication (formerly IP Vault). 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-4536/ (Markdown: https://insights.sbomify.com/CVE-2022-4536/index.md)","id":"CVE-2022-4536","markdown":"https://insights.sbomify.com/CVE-2022-4536/index.md","name":"CVE-2022-4536","record":{"aliases":["GHSA-29xf-xj7q-wj7p"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress firewall plugin","requires_auth":"none","summary":"Attackers can bypass IP-based login restrictions by spoofing the X-Forwarded-For header in the IP Vault WordPress plugin.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"two-factor_authentication","vendor":"youtag"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-348","name":"Use of Less Trusted Source"}],"description":"The IP Vault – WP Firewall plugin for WordPress is vulnerable to IP Address Spoofing in versions up to, and including, 1.1. This is due to insufficient restrictions on where the IP Address information is being retrieved for request logging and login restrictions. Attackers can supply the X-Forwarded-For header with with a different IP Address that will be logged and can be used to bypass settings that may have blocked out an IP address or country from logging in.","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":"IP Vault – WP Firewall \u003c= 1.1 - IP Address Spoofing to Protection Mechanism Bypass","id":"CVE-2022-4536","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Hide My WP Ghost – Security Plugin \u003c= 5.0.18 - IP Address Spoofing to Protection Mechanism Bypass","id":"CVE-2022-4537"},"packages":[],"prev":{"headline":"Limit Login Attempts (Spam Protection) \u003c= 5.3 - IP Address Spoofing to Protection Mechanism Bypass","id":"CVE-2022-4534"},"products":["Two-factor authentication (formerly IP Vault)"],"published":"2024-08-31","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["youtag"]},"summary":"Attackers can bypass IP-based login restrictions by spoofing the X-Forwarded-For header in the IP Vault WordPress plugin.","url":"https://insights.sbomify.com/CVE-2022-4536/"}