B1.lt for WooCommerce <= 2.2.57 - Missing Authorization to Authenticated (Subscriber+) Arbitrary SQL Injection
Strategic Overview
- Status
- Patched in 2.2.58
- Affected Plugin
- Site.pro for WooCommerce
- Affected Version
<= 2.2.57- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-6718
At a glance
CVE-2025-6718 is a high-severity Missing Authorization vulnerability in the Site.pro for WooCommerce WordPress plugin, affecting versions <= 2.2.57. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.2.58; sites on affected versions should update now. Disclosed July 2025, reported by Aurélien BOURDOIS (Elymaro).
Vulnerability Overview
The B1.lt plugin for WordPress is vulnerable to SQL Injection due to a missing capability check on the b1_run_query AJAX action in all versions up to, and including, 2.2.57. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute and run arbitrary SQL commands.
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-862: Missing Authorization
Reaching this weakness in Site.pro for WooCommerce <= 2.2.57 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Site.pro for WooCommerce the fix is 2.2.58: builds <= 2.2.57 are affected, anything from 2.2.58 onward is not.
Remediation
Update to version 2.2.58, or a newer patched version
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. None of that substitutes for the fix: Site.pro for WooCommerce 2.2.58 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Site.pro for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C