WordPress IDPay Payment Gateway for Woocommerce plugin <= 2.2.5 - Sensitive Data Exposure vulnerability

published 2026-06-15 4mo ago modified 2026-10-25 15d ago also EUVD-2026-36918

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits: 0; none known

Unauthenticated Sensitive Data Exposure in IDPay Payment Gateway for Woocommerce <= 2.2.5 versions.

Is CVE-2026-34891 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 4mo ago (2026-06-16)

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

IDPay IDPay Payment Gateway for Woocommerce

Classification

Weakness

CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/woo-idpay-gateway/vulnerability/wordpress-idpay-payment-gateway-for-woocommerce-plu
vdb-entry

Sources

CVE List CVE-2026-34891
NVD CVE-2026-34891

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.