Is AweBooking safe to use?

Laskyr does not give safety verdicts. The latest version (3.2.26) has 1 known unpatched vulnerability. As of 2026-11-04, the sources we check list the newest release of AweBooking as affected and name no fixed version yet. Keep AweBooking on the latest version (3.2.26) and remove it if you do not use it.

Which versions of AweBooking are vulnerable?

Known issues on record (newest first): Information disclosure (3.2.26 and older). The full list with sources is on this page.

What is the latest version of AweBooking?

3.2.26, according to wordpress.org (last updated 2019-10-07). It has 1,000+ active installs.

What should I do if my AweBooking is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update awebooking). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · awebooking · data as of 2026-11-04

Is AweBooking safe? Known vulnerabilities and latest version

Latest version: 3.2.26
Last updated: 2019-10-07
Active installs: 1,000+
Known issues on record: 1
Unpatched in latest: 1
Tested up to WP: 5.2.30 · PHP 5.6+

Awebooking helps you to setup hotel booking system quickly, pleasantly and easily. — by awethemes

What to do

There is no fixed version yet. If you can live without AweBooking for now, deactivate it and delete it until the developer ships a fix.
If you must keep it, limit who can log in (remove unused accounts, especially low-level ones) and put a web application firewall in front of the site.
Watch for an update: get an email when this page changes.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI: wp plugin get awebooking --field=version shows what you run; wp plugin update awebooking updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.5 affects latest 3.2.26 CVE-2025-68014 · published 2026-01-05

Information disclosure in AweBooking (3.2.26 and older)

Affected: 3.2.26 and older
Fixed in: no fix listed yet
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Insertion of Sensitive Information Into Sent Data vulnerability in awethemes AweBooking awebooking allows Retrieve Embedded Sensitive Data.This issue affects AweBooking: from n/a through <= 3.2.26.

NVD CVE-2025-68014 Patchstack advisory

Recent activity

2019-10-07 — latest release on wordpress.org (3.2.26).
2026-01-05 — Information disclosure disclosed (CVE-2025-68014), no fix listed yet.

Free. We check the CVE feeds every day and email you only when a new issue for AweBooking (awebooking) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Sensitive data exposure (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/awebooking (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/awebooking"><img src="https://laskyr.com/plugins/awebooking/badge.svg" alt="AweBooking vulnerability status"></a>

← Check another plugin · Free hacked-site scan