B1.lt for WooCommerce Plugin up to 1.lt/2.2.56 on WordPress ID sql injection

Summaryinfo

A vulnerability marked as critical has been reported in B1.lt for WooCommerce Plugin up to 1.lt/2.2.56 on WordPress. Affected by this vulnerability is an unknown functionality. This manipulation of the argument ID causes sql injection. The identification of this vulnerability is CVE-2025-6717. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in B1.lt for WooCommerce Plugin up to 1.lt/2.2.56 on WordPress. It has been declared as critical. Affected by this vulnerability is an unknown code. The manipulation of the argument id with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

The B1.lt plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter in all versions up to, and including, 2.2.56 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

The advisory is shared at wordfence.com. This vulnerability is known as CVE-2025-6717 since 06/26/2025. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/18/2025). MITRE ATT&CK project uses the attack technique T1505 for this issue.

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

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21848). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• E-Commerce Management Software

Name

• B1.lt for WooCommerce Plugin

Version

• 1.la
• 1.lb
• 1.lc
• 1.ld
• 1.le
• 1.lf
• 1.lg
• 1.lh
• 1.li
• 1.lj
• 1.lk
• 1.ll
• 1.lm
• 1.ln
• 1.lo
• 1.lp
• 1.lq
• 1.lr
• 1.ls
• 1.lt
• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3
• 2.2.4
• 2.2.5
• 2.2.6
• 2.2.7
• 2.2.8
• 2.2.9
• 2.2.10
• 2.2.11
• 2.2.12
• 2.2.13
• 2.2.14
• 2.2.15
• 2.2.16
• 2.2.17
• 2.2.18
• 2.2.19
• 2.2.20
• 2.2.21
• 2.2.22
• 2.2.23
• 2.2.24
• 2.2.25
• 2.2.26
• 2.2.27
• 2.2.28
• 2.2.29
• 2.2.30
• 2.2.31
• 2.2.32
• 2.2.33
• 2.2.34
• 2.2.35
• 2.2.36
• 2.2.37
• 2.2.38
• 2.2.39
• 2.2.40
• 2.2.41
• 2.2.42
• 2.2.43
• 2.2.44
• 2.2.45
• 2.2.46
• 2.2.47
• 2.2.48
• 2.2.49
• 2.2.50
• 2.2.51
• 2.2.52
• 2.2.53
• 2.2.54
• 2.2.55
• 2.2.56

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