Vulnerability feed

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

Critical in the last 24 hours

1603 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

144-76% vs 7-day avg of 597

2 critical, 38 high, 59 medium, 25 low

Expand	Severity	Score	Advisory	Title	Source	Flags	Published
	Unknown	n/a	CVE-2026-110285	The WP Stripe Checkout WordPress plugin before 1.2.2.62 does not verify the Stripe webhook signature when no signing secret is configured, which is its default state, allowing... WP Stripe CheckoutWP Stripe Checkout wp-stripe-checkout	NVD		Oct 25 06:16 UTC
CVE-2026-110285The WP Stripe Checkout WordPress plugin before 1.2.2.62 does not verify the Stripe webhook signature when no signing secret is configured, which is its default state, allowing... Executive summary The WP Stripe Checkout WordPress plugin contains a flaw that lets an attacker bypass authentication for Stripe webhook requests. The advisory rates it medium severity with a CVSS score of 5.3 and says it is fixed in version 1.2.2.62. Technical summary The flaw is classified as an authentication bypass (CWE-287) in which the plugin does not verify the Stripe webhook signature when no signing secret is configured, which the advisory says is the default state. The attack vector is network-based, and the advisory indicates the attacker can gain access without authentication, but the exact impact beyond that is cut off in the text. Affected versions are stated as before 1.2.2.62, and the fixed version is 1.2.2.62. No workaround is stated. No detection guidance or evidence of exploitation in the wild is stated. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from wpscan.com/vulnerability/0f32d471-2806-…71-9a82-87895ef903ae Score No CVSS score published. Affects WP Stripe Checkout WP Stripe Checkout wp-stripe-checkout NIST National Vulnerability DatabasePublished Oct 25, 2026 06:16 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