CVE-2025-11632 MEDIUM

CVE-2025-11632: Call Now Button <= 1.5.4 - Authenticated (Subscriber+) Missing Authorization to Multiple Functions

Vendor Jgrietveld
Product Call Now Button – The #1 Click to Call Button for WordPress
Weakness CWE-862 · Missing authorization
Published October 29, 2025
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

What the vulnerability does

01Description

The Call Now Button – The #1 Click to Call Button for WordPress plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on multiple functions in all versions up to, and including, 1.5.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to generate links to billing portal, where they can view and modify billing information of the connected, account, generate chat session tokens, view domain status, etc. This vulnerability was partially fixed in version 1.5.4 and fully fixed in version 1.5.5

Explanation of Vulnerability in Simple Terms

02Summary

The Call Now Button plugin for WordPress does not properly check user permissions before allowing access to certain functions. A logged-in user with low privileges can read sensitive data they should not have access to. The vulnerability affects all versions up to 1.5.4. Site administrators should update the plugin as soon as a patched version is available.

What an attacker can do

03Attacker Capabilities

Read sensitive data they should not have access to as a low-privilege user.

Potential impact on your site

04Site Impact

Unauthorized users can access private plugin data or settings, potentially exposing configuration details.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress user account (e.g., subscriber or contributor).

Key dates

06Disclosure timeline

October 29, 2025 CVE published
April 8, 2026 Record updated