{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4911 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4911 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4911 is a medium-severity vulnerability in masaakitanaka Booking Package, published on 28 Apr 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-4911 and fix it if it is affected.\n\nWhat it is: CVE-2026-4911 is a medium-severity vulnerability in masaakitanaka Booking Package, published on 28 Apr 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-4911 in the wild and no public exploit code.\n\nAffected product: masaakitanaka Booking Package. 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-4911/ (Markdown: https://insights.sbomify.com/CVE-2026-4911/index.md)","id":"CVE-2026-4911","markdown":"https://insights.sbomify.com/CVE-2026-4911/index.md","name":"CVE-2026-4911","record":{"aliases":["GHSA-2276-pc6c-j8wg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress booking plugin","requires_auth":"none","summary":"Unauthenticated attackers can manipulate booking prices by bypassing server-side validation, allowing them to purchase services at arbitrary low costs.","user_interaction":"not_required","vuln_class":"business_logic"},"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:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-472","name":"External Control of Assumed-Immutable Web Parameter"}],"description":"The Booking Package plugin for WordPress is vulnerable to Price Manipulation in versions up to, and including, 1.7.06 This is due to the intentForStripe() function passing user-controlled $_POST['amount'] directly to the Stripe PaymentIntent API without validation, and the commitStripe() function ignoring the server-calculated amount when confirming the payment. While the server correctly calculates the booking cost via getAmount() based on services, guests, taxes, and coupons, this calculated amount is never validated against or used to update the PaymentIntent because the critical code in CreditCard.php that would include the calculated amount in the PaymentIntent update is commented out. This makes it possible for unauthenticated attackers to book services at arbitrary prices (e.g., $0.01 instead of $500.00) by manipulating the amount parameter during PaymentIntent creation and completing the booking with the fraudulent payment.","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 Package \u003c= 1.7.06 - Unauthenticated Price Manipulation via 'amount' Parameter","id":"CVE-2026-4911","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Media Cleaner: Clean your WordPress! \u003c= 7.0.3 - Authenticated (Administrator+) Server-Side Request Forgery","id":"CVE-2026-4912"},"packages":[],"prev":{"headline":"Shenzhen Ruiming Technology Streamax Crocus Endpoint RemoteFormat.do sql injection","id":"CVE-2026-4910"},"products":["Booking Package"],"published":"2026-04-28","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-04-29","vendors":["masaakitanaka"]},"summary":"Unauthenticated attackers can manipulate booking prices by bypassing server-side validation, allowing them to purchase services at arbitrary low costs.","url":"https://insights.sbomify.com/CVE-2026-4911/"}