{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-15823 exists.","fix":"No fix has been published for CVE-2019-15823 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15823 is a critical vulnerability in n/a, published on 30 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15823 and fix it if it is affected.\n\nWhat it is: CVE-2019-15823 is a critical vulnerability in n/a, published on 30 Aug 2019. 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-2019-15823 exists.\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-2019-15823/ (Markdown: https://insights.sbomify.com/CVE-2019-15823/index.md)","id":"CVE-2019-15823","markdown":"https://insights.sbomify.com/CVE-2019-15823/index.md","name":"CVE-2019-15823","record":{"aliases":["GHSA-q98w-m2p3-q3ff"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can bypass the login protection mechanism in the wps-hide-login WordPress plugin, potentially exposing the login page.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wps_hide_login","vendor":"wpserveur"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"The wps-hide-login plugin before 1.5.3 for WordPress has an action=confirmaction protection bypass.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2019/CVE-2019-15823.yaml","stars":null,"title":"WPS Hide Login \u003c= 1.5.2.2  - Login Page Bypass"}],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2019-15823","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2019-15824"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2019-15822"},"products":["n/a"],"published":"2019-08-30","related":[{"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass the login protection mechanism in the wps-hide-login WordPress plugin, potentially exposing the login page.","url":"https://insights.sbomify.com/CVE-2019-15823/"}