Awethemes AweBooking Plugin up to 3.2.26 on WordPress insertion of sensitive information into sent data

Summaryinfo

A vulnerability classified as problematic has been found in Awethemes AweBooking Plugin up to 3.2.26 on WordPress. This issue affects some unknown processing. This manipulation causes insertion of sensitive information into sent data. This vulnerability is handled as CVE-2025-68014. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Awethemes AweBooking Plugin up to 3.2.26 on WordPress. It has been declared as problematic. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a insertion of sensitive information into sent data vulnerability. The CWE definition for the vulnerability is CWE-201. The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. As an impact it is known to affect confidentiality. The summary by CVE is:

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

The weakness was released by Numex. The advisory is shared at vdp.patchstack.com. This vulnerability is known as CVE-2025-68014 since 12/15/2025. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/05/2026). MITRE ATT&CK project uses the attack technique T1592 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Vendor

• Awethemes

Name

• AweBooking Plugin

Version

• 3.2.0
• 3.2.1
• 3.2.2
• 3.2.3
• 3.2.4
• 3.2.5
• 3.2.6
• 3.2.7
• 3.2.8
• 3.2.9
• 3.2.10
• 3.2.11
• 3.2.12
• 3.2.13
• 3.2.14
• 3.2.15
• 3.2.16
• 3.2.17
• 3.2.18
• 3.2.19
• 3.2.20
• 3.2.21
• 3.2.22
• 3.2.23
• 3.2.24
• 3.2.25
• 3.2.26

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion