WP Manifestindependent plugin directory
manifest / events / wp-booking-engine

Booking Engine WP Registry grade D+. High-severity findings · 2 findingsWP RegistryHigh-severity findings · 2 findingsOpen the reportD+

Easy Omnibees Booking Engine for Wordpress

★ 4stars
5.2.0latest · 1 year ago

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/thallysondias/wp-booking-engine/archive/refs/heads/master.zip
Updates itself. It ships its own updater (Plugin Update Checker), so new versions appear under Dashboard → Updates.

Description

Through this plugin your site will have the possibility to book direct reservations to the Omnibees reservation system. In order to use it is necessary to have the unique reservation ID generated by Omnibees.

Omnibees customers can access this number trought this email: servicedesk@omnibees.com.

The plugin has two layout, fixed in the bottom bar of the website or off-canvas. You can customize the language and colors of the booking engine.

Supported languages

  • English
  • Portuguese (pt/br)
  • Spanish

Installation

The Booking Engine will be automatically inserted into the website

Frequently Asked Questions

What do I need to use the plugin?

It is only necessary that you have the Reservation ID generated by Omnibees. This number can be requested by email: servicedesk@omnibees.com

Screenshots

Admin Panel

Releases

Newest 25 of 29 recorded releases.

Tag
Published
5.2.0 latest
Dec 27, 2024 1 year ago
Oct 15, 2024 2 years ago
Jul 3, 2024 2 years ago
Jun 26, 2024 2 years ago
5.1
Jun 24, 2024 2 years ago
5.0
Nov 14, 2023 2 years ago
Sep 27, 2023 3 years ago
4.2
Sep 18, 2023 3 years ago
4.1
Sep 11, 2023 3 years ago
Jun 16, 2022 4 years ago
Jun 15, 2022 4 years ago
Jun 15, 2022 4 years ago
Nov 11, 2021 4 years ago
Jun 24, 2021 5 years ago
Jun 24, 2021 5 years ago
Jun 18, 2021 5 years ago
Jun 18, 2021 5 years ago
May 13, 2021 5 years ago
May 13, 2021 5 years ago
May 7, 2020 6 years ago
Apr 29, 2020 6 years ago
Mar 12, 2020 6 years ago
Mar 12, 2020 6 years ago
Mar 12, 2020 6 years ago
Mar 12, 2020 6 years ago
All releases on GitHub →

These releases are tags only. The author does not attach a packaged zip, so there are no download counts to report.

D+ grade

Security

Booking Engine 5.2.0 · audited by WP Registry

High-severity findings.

2 high
Audited release
5.2.0
Findings
2
Worst severity
high
Content hash
5054d0e38d33f3e495f27363…

Findings

  • high Missing nonce on booking settings save enables CSRF to stored front-end XSS

    csrf

    admin/customize-be.php runs be_opt() on any POST with be_submit while the page is loaded. There is no wp_nonce_field/check_admin_referer. An attacker can CSRF a manage_options user into writing arbitrary values into omnibees_bg, omnibees_texto, omnibees_botao, omnibees_url, hotel_id, and affiliate. Those options are echoed unescaped into front-end widget CSS and form attributes (views/*/booking-widget.php), so CSRF can inject </style><script>…</script> (stored XSS/skimmer) or redirect bookings via omnibees_url/hotel_id.

    admin/customize-be.php:3-56

    Recommendation

    Add check_admin_referer before be_opt(); sanitize colors (sanitize_hex_color), URLs (esc_url_raw), and escape all get_option outputs in views with esc_attr/esc_url.

  • high Unescaped omnibees_* options echoed into front-end CSS and form attributes

    xss_stored

    Booking widget templates echo get_option('omnibees_bg'), omnibees_texto, omnibees_botao, omnibees_idioma, affiliate, and form action URLs without escaping. Combined with unsanitized admin saves, any value stored in those options executes in visitors' browsers (CSS breakout) or controls the booking destination.

    views/off-canvas/booking-widget.php:8-115

    Recommendation

    Escape every option echo (esc_attr for CSS/color and attributes, esc_url for action). Validate allowed templates/idiomas against a whitelist.

WP Registry hashes the installable build and reports on that exact bytes-for-bytes copy. Embargoed findings are withheld until they are disclosed, so a clean verdict means nothing public is outstanding. WP Manifest does not audit code itself.