{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-12905 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12905 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12905 is a medium-severity vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 16 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-12905 and fix it if it is affected.\n\nWhat it is: CVE-2026-12905 is a medium-severity vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 16 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-12905 in the wild and no public exploit code.\n\nAffected product: ladela Online Scheduling and Appointment Booking System – Bookly. 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-12905/ (Markdown: https://insights.sbomify.com/CVE-2026-12905/index.md)","id":"CVE-2026-12905","markdown":"https://insights.sbomify.com/CVE-2026-12905/index.md","name":"CVE-2026-12905","record":{"aliases":["GHSA-j9h8-cf5v-78mc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated staff users can read other staff members' appointment details and customer PII by manipulating the appointment ID parameter.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"The Bookly plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 27.7 via the appointment() method of the Mobile Staff Cabinet API (resource=appointment, action=bookly_mobile_staff_cabinet) in frontend/modules/mobile_staff_cabinet/api/handlers/Handler1_0.php. This is due to the handler loading an Appointment by the attacker-supplied params[id] without verifying that the appointment's staff_id matches the authenticated staff member, whereas sibling operations (deleteAppointment, saveAppointment, appointments list) correctly scope to $this-\u003estaff-\u003egetId() when $this-\u003erole === ROLE_STAFF. This makes it possible for authenticated attackers, with staff-level mobile cabinet access (any valid access_key token bound to a Staff entity), to read appointment details — including the internal note and the full customer_appointments collection (customer full_name, email, phone, notes, custom_fields, extras, payment_total, payment_type, payment_status) — belonging to other staff members by enumerating sequential appointment IDs.","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":"Information disclosure in Online Scheduling and Appointment Booking System – Bookly","id":"CVE-2026-12905","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"RTMKit Addons for Elementor \u003c 2.0.9 - Contributor+ Private Post Title Disclosure","id":"CVE-2026-12906"},"packages":[],"prev":{"headline":"Missing authorization in Kadence Blocks — Page Builder Toolkit for Gutenberg Editor","id":"CVE-2026-12904"},"products":["Online Scheduling and Appointment Booking System – Bookly"],"published":"2026-08-16","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-08-17","vendors":["ladela"]},"summary":"Authenticated staff users can read other staff members' appointment details and customer PII by manipulating the appointment ID parameter.","url":"https://insights.sbomify.com/CVE-2026-12905/"}