CVE-2026-34210 | wevm mppx up to 0.4.10 comparison
VulDBArchived Mar 31, 2026✓ Full text saved
A vulnerability, which was classified as problematic , has been found in wevm mppx up to 0.4.10 . Affected is an unknown function. This manipulation causes incorrect comparison. This vulnerability is tracked as CVE-2026-34210 . The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-354398 · CVE-2026-34210 · GCVE-0-2026-34210
WEVM MPPX UP TO 0.4.10 COMPARISON
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.2 $0-$5k 1.52+
Summaryinfo
A vulnerability, which was classified as problematic, was found in wevm mppx up to 0.4.10. Affected by this vulnerability is an unknown functionality. Such manipulation leads to comparison. This vulnerability is listed as CVE-2026-34210. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.
Detailsinfo
A vulnerability was found in wevm mppx up to 0.4.10 and classified as problematic. Affected by this issue is some unknown functionality. The manipulation with an unknown input leads to a comparison vulnerability. Using CWE to declare the problem leads to CWE-697. The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses. Impacted is integrity, and availability. CVE summarizes:
mppx is a TypeScript interface for machine payments protocol. Prior to version 0.4.11, the stripe/charge payment method did not check Stripe's Idempotent-Replayed response header when creating PaymentIntents. An attacker could replay a valid credential containing the same spt token against a new challenge, and the server would accept the replayed Stripe PaymentIntent as a new successful payment without actually charging the customer again. This allowed an attacker to pay once and consume unlimited resources by replaying the credential. This issue has been patched in version 0.4.11.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-34210 since 03/26/2026. The exploitation is known to be easy. The attack may be launched remotely. The technical details are unknown and an exploit is not available.
Upgrading to version 0.4.11 eliminates this vulnerability.
Productinfo
Vendor
wevm
Name
mppx
Version
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.4.10
Website
Product: https://github.com/wevm/mppx/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Comparison
CWE: CWE-697
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: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: mppx 0.4.11
Timelineinfo
03/26/2026 CVE reserved
03/31/2026 +4 days Advisory disclosed
03/31/2026 +0 days VulDB entry created
03/31/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-34210 (🔒)
GCVE (CVE): GCVE-0-2026-34210
GCVE (VulDB): GCVE-100-354398
Entryinfo
Created: 03/31/2026 16:59
Changes: 03/31/2026 16:59 (65)
Complete: 🔍
Cache ID: 99:14D:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸