{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6292 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6292 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6292 is a medium-severity vulnerability in manuelpadillac MP Customize Login Page, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-6292 and fix it if it is affected.\n\nWhat it is: CVE-2026-6292 is a medium-severity vulnerability in manuelpadillac MP Customize Login Page, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-6292 in the wild and no public exploit code.\n\nAffected product: manuelpadillac MP Customize Login Page. 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-2026-6292/ (Markdown: https://insights.sbomify.com/CVE-2026-6292/index.md)","id":"CVE-2026-6292","markdown":"https://insights.sbomify.com/CVE-2026-6292/index.md","name":"CVE-2026-6292","record":{"aliases":["GHSA-4j34-5678-4gmg"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can modify plugin settings via CSRF by tricking administrators into submitting crafted requests.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The MP Customize Login Page plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF) in all versions up to and including 1.0. This is due to a completely broken nonce validation in the enter_mpclp_login_options() function, which contains an inverted check (if wp_verify_nonce(...) { return false; }) and is missing the required action parameter for wp_verify_nonce(). As a result, the nonce check is effectively dead code: it never blocks malicious requests because a CSRF-supplied empty/invalid nonce always returns false, satisfying the inverted condition to continue execution. Furthermore, the settings-update handler is hooked on init without any capability check. This makes it possible for unauthenticated attackers to modify all plugin setting, including login page background, logo URL, image dimensions, button colors, and login message, by tricking a logged-in administrator into submitting a crafted request.","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":"MP Customize Login Page \u003c= 1.0 - Cross-Site Request Forgery to Settings Update","id":"CVE-2026-6292","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site request forgery in Inquiry form to posts or pages","id":"CVE-2026-6293"},"packages":[],"prev":{"headline":"Bleichenbacher padding oracle in PKCS#7 KTRI RSA PKCS#1 v1.5 decryption","id":"CVE-2026-6291"},"products":["MP Customize Login Page"],"published":"2026-06-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-24","vendors":["manuelpadillac"]},"summary":"Unauthenticated attackers can modify plugin settings via CSRF by tricking administrators into submitting crafted requests.","url":"https://insights.sbomify.com/CVE-2026-6292/"}