CVE-2026-6372 | Plisio Accept Cryptocurrencies with Plugin up to 2.0.5 on WordPress authorization
VulDBArchived Apr 15, 2026✓ Full text saved
A vulnerability categorized as critical has been discovered in Plisio Accept Cryptocurrencies with Plugin up to 2.0.5 on WordPress. Affected by this vulnerability is an unknown functionality. Such manipulation leads to missing authorization. This vulnerability is traded as CVE-2026-6372 . The attack may be launched remotely. There is no exploit available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-357765 · CVE-2026-6372 · GCVE-0-2026-6372
PLISIO ACCEPT CRYPTOCURRENCIES WITH PLUGIN UP TO 2.0.5 ON WORDPRESS AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.3 $0-$5k 2.51+
Summaryinfo
A vulnerability identified as critical has been detected in Plisio Accept Cryptocurrencies with Plugin up to 2.0.5 on WordPress. Affected by this issue is some unknown functionality. Performing a manipulation results in authorization. This vulnerability is known as CVE-2026-6372. Remote exploitation of the attack is possible. No exploit is available.
Detailsinfo
A vulnerability was found in Plisio Accept Cryptocurrencies with Plugin up to 2.0.5 on WordPress. It has been classified as critical. This affects some unknown functionality. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Missing Authorization vulnerability in Plisio Accept Cryptocurrencies with Plisio allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Accept Cryptocurrencies with Plisio: from n/a through 2.0.5.
The weakness was published by Axis. The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2026-6372 since 04/15/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/15/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Type
WordPress Plugin
Vendor
Plisio
Name
Accept Cryptocurrencies with Plugin
Version
2.0.0
2.0.1
2.0.2
2.0.3
2.0.4
2.0.5
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 7.4
VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (Patchstack): 🔒
CVSSv2info
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: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/15/2026 Advisory disclosed
04/15/2026 +0 days CVE reserved
04/15/2026 +0 days VulDB entry created
04/15/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: patchstack.com
Researcher: Axis
Status: Not defined
CVE: CVE-2026-6372 (🔒)
GCVE (CVE): GCVE-0-2026-6372
GCVE (VulDB): GCVE-100-357765
Entryinfo
Created: 04/15/2026 20:05
Changes: 04/15/2026 20:05 (63)
Complete: 🔍
Cache ID: 99:8F9:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸