{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-10100 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-10100 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-10100 is a medium-severity cross-site scripting vulnerability in pattihis Simple Custom Login Page, published on 2 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-10100 and fix it if it is affected.\n\nWhat it is: CVE-2026-10100 is a medium-severity cross-site scripting vulnerability in pattihis Simple Custom Login Page, published on 2 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-10100 in the wild and no public exploit code.\n\nAffected product: pattihis Simple Custom 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-10100/ (Markdown: https://insights.sbomify.com/CVE-2026-10100/index.md)","id":"CVE-2026-10100","markdown":"https://insights.sbomify.com/CVE-2026-10100/index.md","name":"CVE-2026-10100","record":{"aliases":["GHSA-855q-xm3j-j7h8"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Administrators can inject malicious CSS into the WordPress login page, enabling UI-redress and credential phishing attacks against unauthenticated visitors.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/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 Simple Custom Login Page plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the color settings fields (Page Background, Form Background, Text Color, Link Color) in versions up to and including 1.0.3. This is due to insufficient input sanitization of the color option values (they were registered with register_setting() and stored via the Settings API/update_option() with no sanitize_callback) combined with the values being output into a \u003cstyle\u003e block on wp-login.php using esc_attr(), which is incorrect for a CSS context (it does not escape ;, {, }, / or *). This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary CSS rules into the login page that are rendered for all unauthenticated visitors, enabling UI-redress and credential-phishing attacks.","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":"Simple Custom Login Page \u003c= 1.0.3 - Authenticated (Admin+) Stored Cross-Site Scripting","id":"CVE-2026-10100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Assisted-service: assisted-service: infraenv status leaks referenced pull-secret contents to namespace view users","id":"CVE-2026-10101"},"packages":[],"prev":{"headline":"XX-Net V5.16.6 WebSocket Frame Parsing Data Corruption via simple_http_server.py","id":"CVE-2026-10099"},"products":["Simple Custom Login Page"],"published":"2026-06-02","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-02","vendors":["pattihis"]},"summary":"Administrators can inject malicious CSS into the WordPress login page, enabling UI-redress and credential phishing attacks against unauthenticated visitors.","url":"https://insights.sbomify.com/CVE-2026-10100/"}