{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92619 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92619 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92619 is a high-severity vulnerability in wpdevelop Booking Calendar, published on 18 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92619 and fix it if it is affected.\n\nWhat it is: CVE-2026-92619 is a high-severity vulnerability in wpdevelop Booking Calendar, published on 18 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-92619 in the wild and no public exploit code.\n\nAffected product: wpdevelop Booking Calendar. 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-92619/ (Markdown: https://insights.sbomify.com/CVE-2026-92619/index.md)","id":"CVE-2026-92619","markdown":"https://insights.sbomify.com/CVE-2026-92619/index.md","name":"CVE-2026-92619","record":{"aliases":["GHSA-jrfx-j7fq-9588"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Authenticated editors can escalate to administrator by manipulating unregistered WordPress options via the Booking Calendar plugin.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"The Booking Calendar plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 11.8.2 via the `wpbc_ajax_option_save` AJAX action. The vulnerability exists because the `handle_ajax_save()` function applies per-option safeguards only to names explicitly registered via `register_option_policy()`, causing `get_option_policy()` to return an empty policy — bypassing all can_save, force_mode, and allowed_keys checks — for any unregistered option name, including core WordPress options, while an attacker-controlled `data_name` parameter passes through `sanitize_key()` and is written directly to `update_option()` without restriction. This makes it possible for authenticated attackers with Editor-level access and above to escalate their privileges to Administrator by writing core WordPress options such as `default_role=administrator` and `users_can_register=1`, then self-registering a new Administrator account. The nonce check does not meaningfully restrict this attack, as both the nonce value and nonce action are attacker-supplied POST parameters, and a valid nonce is trivially obtainable via `admin-ajax.php?action=rest-nonce`.","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":"Booking Calendar \u003c= 11.8.2 - Authenticated (Editor+) Privilege Escalation to 'data_name' Parameter","id":"CVE-2026-92619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Cross-site scripting in Strong Testimonials","id":"CVE-2026-92622"},"packages":[],"prev":{"headline":"FileRise \u003c 3.28.0 Privilege Escalation via WebDAV Session Inheritance","id":"CVE-2026-92616"},"products":["Booking Calendar"],"published":"2026-09-18","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":"total"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["wpdevelop"]},"summary":"Authenticated editors can escalate to administrator by manipulating unregistered WordPress options via the Booking Calendar plugin.","url":"https://insights.sbomify.com/CVE-2026-92619/"}