πŸ”’
theB10G
  • ⁉️Welcome/whoami
  • πŸ‘¨β€πŸ”¬Malware Analyst for a day
  • πŸ“§Spooky Scammers (Back for the holidays)
  • πŸ’°Hacking the Scammers
  • πŸ’°Systematic Destruction (Hacking the Scammers pt. 2)
  • πŸ€΅β€β™‚οΈSQL Injection in Security Cleared Job Site
  • ↩️XSS Security Policy Bypass
  • πŸ“ŠCraft CMS Unauthenticated SQLi via GraphQL
  • πŸ₯MISI Hack the Building 2.0 Hospital Edition
  • πŸ“”Booked v2.5.5/LabArchives Scheduler Vulnerability
  • πŸ΄β€β˜ οΈCTF Writ3ups
  • πŸͺ–ARCENT Best Cyber Warrior 2023
  • πŸ’΅Bounty Hunter Writeup
  • πŸͺ„Previse Writeup
  • πŸ‘ΎeJPT certification Review
  • πŸ”₯Sauna Writeup
  • πŸƒβ€β™‚οΈActive Writeup
  • 🚘Driver Writeup
  • ❌Trick Writeup
  • πŸ“ŠGraphQL Query Authentication Bypass Vuln
  • πŸ•ΈοΈeWPT Certification Review
  • β˜€οΈ2022 DOE Cyberforce Competition
  • ⛏️Data Mining CVEs and Exploits
  • πŸ’»eCPPTv2 Certification Review
  • Breaking GraphQL Presentation
  • Springshare LibApps Stored XSS
Powered by GitBook
On this page

Was this helpful?

Booked v2.5.5/LabArchives Scheduler Vulnerability

My first CVE? CVE-2023-24058

PreviousMISI Hack the Building 2.0 Hospital EditionNextCTF Writ3ups

Last updated 2 years ago

Was this helpful?

Hey you hackers,

I think I finally found my first CVE. It is a simple one but a new one none the less. This vulnerability in Booked Scheduler, tested on version 2.5.5 and the latest version of LabArchives Schedule, allows for authenticated users to create and schedule events for any other user as long as they have their user ID.

To do this it is as simple as changing the user ID in the HTTP POST request being sent to 'reservation_save.php':

My user ID is not 3 but 159 but changing the request UserId value to 3 created a reservation for the user with ID 3 and this is reflected when you go view the calendar page and see an event under that user name at the time and date specified.

This has been marked as .

πŸ“”
CVE-2023-24058