PublishPress Revisions Plugin up to 3.7.23 on WordPress sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.38 |
Summary
A vulnerability has been found in PublishPress Revisions Plugin up to 3.7.23 on WordPress and classified as critical. Impacted is an unknown function. Performing a manipulation results in sql injection. This vulnerability is identified as CVE-2026-32539. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in PublishPress Revisions Plugin up to 3.7.23 on WordPress. It has been classified as critical. This affects an unknown part. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in PublishPress PublishPress Revisions revisionary allows Blind SQL Injection.This issue affects PublishPress Revisions: from n/a through <= 3.7.23.
The weakness was released by Nguyen Ba Khanh. It is possible to read the advisory at patchstack.com. This vulnerability is uniquely identified as CVE-2026-32539 since 03/12/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. 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 04/01/2026). The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
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
- 3.7.0
- 3.7.1
- 3.7.2
- 3.7.3
- 3.7.4
- 3.7.5
- 3.7.6
- 3.7.7
- 3.7.8
- 3.7.9
- 3.7.10
- 3.7.11
- 3.7.12
- 3.7.13
- 3.7.14
- 3.7.15
- 3.7.16
- 3.7.17
- 3.7.18
- 3.7.19
- 3.7.20
- 3.7.21
- 3.7.22
- 3.7.23
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
ADP CISA Base Score: 9.3
ADP CISA Vector: 🔒
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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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
03/12/2026 CVE reserved03/25/2026 Advisory disclosed
03/25/2026 VulDB entry created
04/01/2026 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: Nguyen Ba Khanh
Status: Not defined
CVE: CVE-2026-32539 (🔒)
GCVE (CVE): GCVE-0-2026-32539
GCVE (VulDB): GCVE-100-353391
Entry
Created: 03/25/2026 19:58Updated: 04/01/2026 10:57
Changes: 03/25/2026 19:58 (55), 04/01/2026 10:57 (12)
Complete: 🔍
Cache ID: 216:D08:103
No comments yet. Languages: en.
Please log in to comment.