{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2473 exists.","fix":"No fix has been published for CVE-2024-2473 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-2473 is a medium-severity vulnerability in tabrisrp WPS Hide Login, published on 11 Jun 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-2024-2473 and fix it if it is affected.\n\nWhat it is: CVE-2024-2473 is a medium-severity vulnerability in tabrisrp WPS Hide Login, published on 11 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2473 exists.\n\nAffected product: tabrisrp WPS Hide Login. 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-2473/ (Markdown: https://insights.sbomify.com/CVE-2024-2473/index.md)","id":"CVE-2024-2473","markdown":"https://insights.sbomify.com/CVE-2024-2473/index.md","name":"CVE-2024-2473","record":{"aliases":["GHSA-cwvf-77f4-2gc5"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can bypass login page hiding features to discover hidden WordPress login URLs, exposing the site to brute-force attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wps_hide_login","vendor":"wpserveur"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The WPS Hide Login plugin for WordPress is vulnerable to Login Page Disclosure in all versions up to, and including, 1.9.15.2. This is due to a bypass that is created when the 'action=postpass' parameter is supplied. This makes it possible for attackers to easily discover any login page that may have been hidden by the plugin.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-03-23","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":1,"refs":[{"date":"2026-03-23T18:32:24Z","kind":"github_poc","ref":"https://github.com/M4xSec/CVE-2024-2473","stars":2,"title":"Wordpress Hidden Login Page Disclosure. Detect Login Page Disclosure in WordPress sites running WPS Hide Login ≤ 1.9.15.2 (CVE-2024-2473)"},{"date":null,"kind":"nuclei","ref":"http/cves/2024/CVE-2024-2473.yaml","stars":null,"title":"WPS Hide Login \u003c= 1.9.15.2 - Login Page Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"WPS Hide Login \u003c= 1.9.15.2 - Login Page Disclosure","id":"CVE-2024-2473","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Standout Color Boxes and Buttons \u003c= 0.7.0 - Authenticated(Contributor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2024-2474"},"packages":[],"prev":{"headline":"LatePoint Plugin \u003c= 4.9.9 - Missing Authorization and Sensitive Information Exposure via IDOR","id":"CVE-2024-2472"},"products":["WPS Hide Login"],"published":"2024-06-11","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2019-15823","kev_date_added":null,"published":"2019-08-30"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2019-15824","kev_date_added":null,"published":"2019-08-30"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2019-15825","kev_date_added":null,"published":"2019-08-30"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2019-15826","kev_date_added":null,"published":"2019-08-30"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2015-9498","kev_date_added":null,"published":"2019-10-22"},{"cvss_score":7.5,"headline":"WPS Hide Login \u003c 1.9.1 - Protection Bypass with Referer-Header","id":"CVE-2021-24917","kev_date_added":null,"published":"2021-12-06"},{"cvss_score":6.1,"headline":"WPS Hide Login \u003c 1.9.16.4 - Hidden Login Page Disclosure","id":"CVE-2024-6289","kev_date_added":null,"published":"2024-07-15"}],"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":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["tabrisrp"]},"summary":"Attackers can bypass login page hiding features to discover hidden WordPress login URLs, exposing the site to brute-force attacks.","url":"https://insights.sbomify.com/CVE-2024-2473/"}