CVE-2025-49950

Official Integration for Billingo <= 4.2.5 - Authenticated (Shop Manager+) Privilege Escalation

2025-07-10 00:00
Martino Spagnuolo

Strategic Overview

Status
Unpatched
Affected Version
<= 4.2.5
CVSS
7.2High
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2025-49950
View all Billingo Official for WooCommerce vulnerabilities

At a glance

CVE-2025-49950 is a high-severity Improper Privilege Management vulnerability in the Billingo Official for WooCommerce WordPress plugin, affecting versions <= 4.2.5. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Shop Manager level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed July 2025, reported by Martino Spagnuolo.

Vulnerability Overview

The Official Integration for Billingo plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.2.5. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to gain administrative-level user access.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-269: Improper Privilege Management

Reaching this weakness in Billingo Official for WooCommerce <= 4.2.5 takes an account at Shop Manager level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. No fixed build of this plugin is recorded for Billingo Official for WooCommerce yet, so installs running <= 4.2.5 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

Other vulnerabilities in Billingo Official for WooCommerce

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C