{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-1912 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-1912 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-1912 is a high-severity cross-site scripting vulnerability in automattic Limit Login Attempts, published on 6 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-1912 and fix it if it is affected.\n\nWhat it is: CVE-2023-1912 is a high-severity cross-site scripting vulnerability in automattic Limit Login Attempts, published on 6 Apr 2023. 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-2023-1912 in the wild and no public exploit code.\n\nAffected product: automattic Limit Login Attempts. 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-1912/ (Markdown: https://insights.sbomify.com/CVE-2023-1912/index.md)","id":"CVE-2023-1912","markdown":"https://insights.sbomify.com/CVE-2023-1912/index.md","name":"CVE-2023-1912","record":{"aliases":["GHSA-wqcw-392x-3hhr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject scripts via lock logs that execute for administrators, requiring the X-FORWARDED-FOR header setting to be enabled.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"limit_login_attempts","vendor":"limit_login_attempts_project"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Limit Login Attempts plugin for WordPress is vulnerable to Stored Cross-Site Scripting via its lock logging feature in versions up to, and including, 1.7.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator accesses the plugin's settings page. This only works when the plugin prioritizes use of the X-FORWARDED-FOR header, which can be configured in its settings.","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":"Limit Login Attempts \u003c= 1.7.1 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2023-1912","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Maps Widget for Google Maps \u003c= 4.24 - Authenticated (Administrator+) Stored Cross-Site Scripting","id":"CVE-2023-1913"},"packages":[],"prev":{"headline":"Blocksy Companion \u003c 1.8.82 - Subscriber+ Draft Post Access","id":"CVE-2023-1911"},"products":["Limit Login Attempts"],"published":"2023-04-06","related":[{"cvss_score":9.8,"headline":"Limit Login Attempts (Spam Protection) \u003c 5.1 - Unauthenticated SQLi","id":"CVE-2022-0787","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2012-10001","kev_date_added":null,"published":"2021-01-06"},{"cvss_score":6.1,"headline":"Limit Login Attempts \u003c 4.0.50 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2021-24657","kev_date_added":null,"published":"2021-09-20"},{"cvss_score":5.4,"headline":"Limit Login Attempts \u003c 1.7.2 - Subscriber+ Stored XSS","id":"CVE-2023-1861","kev_date_added":null,"published":"2023-05-02"}],"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":["automattic"]},"summary":"Unauthenticated attackers can inject scripts via lock logs that execute for administrators, requiring the X-FORWARDED-FOR header setting to be enabled.","url":"https://insights.sbomify.com/CVE-2023-1912/"}