{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-87835 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-87835 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-87835 is a medium-severity vulnerability in Unknown Front End Users, published on 24 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-87835 and fix it if it is affected.\n\nWhat it is: CVE-2026-87835 is a medium-severity vulnerability in Unknown Front End Users, published on 24 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-87835 in the wild and no public exploit code.\n\nAffected product: Unknown Front End Users. 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-87835/ (Markdown: https://insights.sbomify.com/CVE-2026-87835/index.md)","id":"CVE-2026-87835","markdown":"https://insights.sbomify.com/CVE-2026-87835/index.md","name":"CVE-2026-87835","record":{"aliases":["GHSA-jmq3-353m-7wg2"],"analysis":null,"analysis_generated_by":null,"assigner":"WPScan","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"The Front End Users WordPress plugin through 3.2.35 does not restrict which account attributes a visitor may set when registering through its front-end forms, allowing unauthenticated users to assign themselves an arbitrary membership level and to mark their own account as approved, confirmed and paid, bypassing the Front End Users WordPress plugin through 3.2.35's content restrictions and its registration gating.","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":"Front End Users \u003c= 3.2.35 - Unauthenticated Membership Level and Account Status Self-Assignment","id":"CVE-2026-87835","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Comments Import \u0026 Export 2.1.11 - 2.5.3 - Author+ Comment PII Disclosure via Export","id":"CVE-2026-87836"},"packages":[],"prev":{"headline":"Checkout Field Manager \u003c 7.9.7 - Subscriber+ Arbitrary Attachment Deletion via Customer Address Custom Field","id":"CVE-2026-87831"},"products":["Front End Users"],"published":"2026-10-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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-24","vendors":["Unknown"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-87835/"}