{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35590 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35590 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35590 is a critical vulnerability in n/a, published on 21 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-35590 and fix it if it is affected.\n\nWhat it is: CVE-2020-35590 is a critical vulnerability in n/a, published on 21 Dec 2020. 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-2020-35590 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2020-35590/ (Markdown: https://insights.sbomify.com/CVE-2020-35590/index.md)","id":"CVE-2020-35590","markdown":"https://insights.sbomify.com/CVE-2020-35590/index.md","name":"CVE-2020-35590","record":{"aliases":["GHSA-ch2j-pqr2-h9jh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can bypass login rate limits in the Limit Login Attempts Reloaded WordPress plugin by forging the X-Forwarded-For header when configured to trust arbitrary headers.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"limit_login_attempts_reloaded","vendor":"limitloginattempts"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"LimitLoginAttempts.php in the limit-login-attempts-reloaded plugin before 2.17.4 for WordPress allows a bypass of (per IP address) rate limits because the X-Forwarded-For header can be forged. When the plugin is configured to accept an arbitrary header for the client source IP address, a malicious user is not limited to perform a brute force attack, because the client IP header accepts any arbitrary string. When randomizing the header input, the login count does not ever reach the maximum allowed retries.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-12-23","github_poc":1,"max_poc_stars":8,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-12-23T23:11:34Z","kind":"github_poc","ref":"https://github.com/N4nj0/CVE-2020-35590","stars":8,"title":"Brute-force tool for WordPress Plugin Limit Login Attempts Reloaded \u003e=2.13.0 - Login Limit Bypass (CVE-2020-35590)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2020-35590","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2020-35591"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-35589"},"products":["n/a"],"published":"2020-12-21","related":[{"cvss_score":6.4,"headline":"Limit Login Attempts Reloaded \u003c= 2.25.26 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2023-6934","kev_date_added":null,"published":"2024-01-11"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2020-35589","kev_date_added":null,"published":"2020-12-21"},{"cvss_score":4.3,"headline":"Limit Login Attempts Reloaded \u003c 2.25.26 - Admin+ Missing Authorization to Toggle Plugin Auto-Update","id":"CVE-2023-5525","kev_date_added":null,"published":"2023-11-27"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can bypass login rate limits in the Limit Login Attempts Reloaded WordPress plugin by forging the X-Forwarded-For header when configured to trust arbitrary headers.","url":"https://insights.sbomify.com/CVE-2020-35590/"}