{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103365 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103365 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103365 is a medium-severity vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-103365 and fix it if it is affected.\n\nWhat it is: CVE-2026-103365 is a medium-severity vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-103365 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-103365/ (Markdown: https://insights.sbomify.com/CVE-2026-103365/index.md)","id":"CVE-2026-103365","markdown":"https://insights.sbomify.com/CVE-2026-103365/index.md","name":"CVE-2026-103365","record":{"aliases":["GHSA-5p6p-rjcr-26xj"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress booking plugin","requires_auth":"none","summary":"Unauthenticated attackers can read stored customer personal data by exploiting a logic flaw in the booking details endpoint if specific placeholders are configured.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Bookly – Online Scheduling and Appointment Booking System plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 28.4 via the classic booking form's Details step. The endpoint bookly_render_details is registered for both wp_ajax and wp_ajax_nopriv, the module overrides csrfTokenValid() to always return true, and Bookly\\Frontend\\Components\\Booking\\InfoText::getCodes() calls UserBookingData::getCustomer() to load the persisted Customer entity keyed solely by the attacker-supplied phone (or email) with no invocation of the plugin's own customerIdentityConfirmed() predicate. When a site owner has placed the supported {client_name}, {client_email}, {client_phone}, or {client_note} placeholders into the Details step's Appearance information text, the matched customer's stored name, email, phone and internal notes are substituted into the returned HTML. This makes it possible for unauthenticated attackers who know only a registered customer's primary phone (or email) to read that customer's stored personal data.","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-103365","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":"Information disclosure in Appointment Booking Plugin – LatePoint | Calendar \u0026 Scheduling for WordPress","id":"CVE-2026-103366"},"packages":[],"prev":{"headline":"Langflow OSS is affected by multiple vulnerabilities","id":"CVE-2026-103360"},"products":["Online Scheduling and Appointment Booking System – Bookly"],"published":"2026-10-10","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-11","vendors":["ladela"]},"summary":"Unauthenticated attackers can read stored customer personal data by exploiting a logic flaw in the booking details endpoint if specific placeholders are configured.","url":"https://insights.sbomify.com/CVE-2026-103365/"}