{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-13821 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-13821 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-13821 is a medium-severity vulnerability in wpdevelop Booking Calendar, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-13821 and fix it if it is affected.\n\nWhat it is: CVE-2024-13821 is a medium-severity vulnerability in wpdevelop Booking Calendar, published on 12 Feb 2025. 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-2024-13821 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-2024-13821/ (Markdown: https://insights.sbomify.com/CVE-2024-13821/index.md)","id":"CVE-2024-13821","markdown":"https://insights.sbomify.com/CVE-2024-13821/index.md","name":"CVE-2024-13821","record":{"aliases":["GHSA-qw84-q4qh-xxpc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can manipulate confirmed bookings in WP Booking Calendar due to missing re-verification, allowing unauthorized data modification.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"booking_calendar","vendor":"wpbookingcalendar"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"The WP Booking Calendar plugin for WordPress is vulnerable to Unauthenticated Post-Confirmation Booking Manipulation in all versions up to, and including, 10.10. This is due to the plugin not properly requiring re-verification after a booking has been made and a change is being attempted. This makes it possible for unauthenticated attackers to manipulate their confirmed bookings, even after they have been approved.","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":"WP Booking Calendar \u003c= 10.10 - Unauthenticated Post-Confirmation Booking Manipulation","id":"CVE-2024-13821","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Total Contest Lite \u003c= 2.8.1 - Reflected XSS","id":"CVE-2024-13822"},"packages":[],"prev":{"headline":"Melhor Envio \u003c= 2.15.11 - Unauthenticated Sensitive Information Exposure via Hardcoded Hash","id":"CVE-2024-13820"},"products":["Booking Calendar"],"published":"2025-02-12","related":[{"cvss_score":9.8,"headline":"Booking Calendar \u003c= 9.9 - Unauthenticated SQL Injection","id":"CVE-2024-1207","kev_date_added":null,"published":"2024-02-08"},{"cvss_score":6.5,"headline":"WordPress Booking Calendar Plugin \u003c 9.7.4 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-51520","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":6.4,"headline":"WP Booking Calendar \u003c= 10.2.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via bookingform Shortcode","id":"CVE-2024-6930","kev_date_added":null,"published":"2024-07-24"},{"cvss_score":6.1,"headline":"Booking Calendar \u003c 9.7.3.1 - Unauthenticated Stored XSS","id":"CVE-2023-4620","kev_date_added":null,"published":"2023-10-16"},{"cvss_score":5.4,"headline":"WordPress Booking Calendar plugin \u003c= 9.2.1 - Cross-Site Request Forgery (CSRF) vulnerabiulity","id":"CVE-2022-33177","kev_date_added":null,"published":"2022-09-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-06-03","vendors":["wpdevelop"]},"summary":"Unauthenticated attackers can manipulate confirmed bookings in WP Booking Calendar due to missing re-verification, allowing unauthorized data modification.","url":"https://insights.sbomify.com/CVE-2024-13821/"}