ThemesGrove WP SmartPay Plugin up to 2.7.13 on WordPress Input Vulnerability improper validation of specified quantity in input
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in ThemesGrove WP SmartPay Plugin up to 2.7.13 on WordPress. The affected element is an unknown function of the component Input Vulnerability. This manipulation causes improper validation of specified quantity in input. This vulnerability is registered as CVE-2025-32689. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in ThemesGrove WP SmartPay Plugin up to 2.7.13 on WordPress. It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the component Input Vulnerability. The manipulation with an unknown input leads to a improper validation of specified quantity in input vulnerability. The CWE definition for the vulnerability is CWE-1284. The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties. As an impact it is known to affect integrity. The summary by CVE is:
Improper Validation of Specified Quantity in Input vulnerability in ThemesGrove WP SmartPay. This issue affects WP SmartPay: from n/a through 2.7.13.
The weakness was published by Abdi Pranata. It is possible to read the advisory at patchstack.com. This vulnerability is known as CVE-2025-32689 since 04/09/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/09/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (Patchstack): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper validation of specified quantity in inputCWE: CWE-1284 / CWE-703
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/09/2025 CVE reserved09/09/2025 Advisory disclosed
09/09/2025 VulDB entry created
09/09/2025 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: Abdi Pranata
Status: Not defined
CVE: CVE-2025-32689 (🔒)
GCVE (CVE): GCVE-0-2025-32689
GCVE (VulDB): GCVE-100-323395
Entry
Created: 09/09/2025 23:10Changes: 09/09/2025 23:10 (64)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.