Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 08:05 UTC

Critical in the last 24 hours

1601 in 30 days

Newly known exploited

In the last 24 hours, CISA KEV and vendor reports

Sources checked

Every hour, see the list

New in the last 24 hours

181-70% vs 7-day avg of 598

2 critical, 65 high, 73 medium, 31 low

Expand	Severity	Score	Advisory	Title	Source	Flags	Published
	Unknown	n/a	CVE-2026-103381	The Mintpay for WooCommerce WordPress plugin through 2.2.3 does not verify the authenticity of the payment callback it processes, allowing unauthenticated attackers to mark... MintpayMintpay for WooCommerce	NVD		Oct 26 07:17 UTC
CVE-2026-103381The Mintpay for WooCommerce WordPress plugin through 2.2.3 does not verify the authenticity of the payment callback it processes, allowing unauthenticated attackers to mark... Executive summary The Mintpay for WooCommerce WordPress plugin, through version 2.2.3, has a flaw that lets unauthenticated attackers mark payments as completed without a genuine payment. The advisory describes this as a medium severity issue with a CVSS score of 6.5, and it states no known fix is available. Technical summary The flaw is a broken access control issue (CWE-284) in which the plugin does not verify the authenticity of the payment callback it processes, allowing unauthenticated attackers to mark payments as paid. The attack requires no authentication, and the advisory's details on the exact request path are not stated. Affected versions are stated as through 2.2.3. No fixed version is stated, and the advisory says there is no known fix. Workarounds are not stated. Detection guidance is not stated. The advisory's text is truncated, so further detail may be missing. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from wpscan.com/vulnerability/593fa052-8917-…6c-944b-11b890c9ab50 Score No CVSS score published. Affects Mintpay Mintpay for WooCommerce NIST National Vulnerability DatabasePublished Oct 26, 2026 07:17 UTC Read the advisory

Example	Finds
	Every word appears somewhere: title, summaries, IDs, vendor, or product
	An exact phrase
	One vendor. product: for a product, vp: for either
	Commas mean any of them, in every field
	Severity: critical, high, medium, low, or unknown
	CVSS score, with >, >=, <, or <=
	A score range
	Known exploited. is:kev works too, and kev:no leaves them out
	One source, by name
	Confidentiality impact: high, low, none, or any (low or high)
	Integrity and availability work the same way
	An advisory or CVE ID, or part of one
	A minus sign leaves out whatever the term matches

Vulnerability feed

Executive summary

Technical summary

Score

Affects

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee