Normal view
-
/r/netsec - Information Security News & Discussion
- I Missed One TLB Shootdown and Somehow Ended Up Controlling a Page Table
N0va Phishkit Targets US and EU Businesses: A New Challenge for Identity Security
Threat Intelligence Alone Won't Close the Exploitation Gap
-
The Hacker News
- Attack Chains, Not Just Attack Surfaces: Why Testing Individual Techniques Misses the Point
Attack Chains, Not Just Attack Surfaces: Why Testing Individual Techniques Misses the Point
US Becomes Top Target in RMM Phishing Campaign Spanning 46 Countries
Shai-Hulud's Reach Just Grew to 469 Credential Locations. Here's What That Means
-
The Hacker News
- CISA Adds Seven Exploited Flaws as Attackers Deploy Reverse Shells and Crypto Miners
CISA Adds Seven Exploited Flaws as Attackers Deploy Reverse Shells and Crypto Miners
Meta Ads Push StreamRat Android Trojan That Can Gain Near-Complete Device Control
How to Secure Enterprise AI: From Adoption to Incident Readiness
Threat Actors Donβt Want Better Attacks. They Want Repeatable Ones
-
The Hacker News
- Securing Claude Code: The New Compliance API, Local Visibility, and Identity Governance
Securing Claude Code: The New Compliance API, Local Visibility, and Identity Governance
Key Reasons Why Identity Fabric Matters in 2026
-
/r/netsec - Information Security News & Discussion
- A fake resume invoked Chinaβs defence tech elite, then installed VShell
A fake resume invoked Chinaβs defence tech elite, then installed VShell
-
/r/netsec - Information Security News & Discussion
- Chaining three public V8 bugs to escape the V8 sandbox and recover a real Google v8CTF flag
-
/r/netsec - Information Security News & Discussion
- ValleyRAT campaign uses fake GSTR-3B overdue notice targeting Indian taxpayers
ValleyRAT campaign uses fake GSTR-3B overdue notice targeting Indian taxpayers
-
/r/netsec - Information Security News & Discussion
- CVE-2026-53360: KVM SEV-SNP guest-to-host heap OOB and analysis of the upstream fix
CVE-2026-53360: KVM SEV-SNP guest-to-host heap OOB and analysis of the upstream fix
-
/r/netsec - Information Security News & Discussion
- I was reporter #11 for a WPForms PayPal webhook vulnerability (CVE-2026-4986)
I was reporter #11 for a WPForms PayPal webhook vulnerability (CVE-2026-4986)
I found and reported an authentication failure in the WPForms PayPal Commerce webhook, the webhook route being public was not the vulnerability as webhooks have to be publicly reachable so that PayPal can deliver events.
The problem was what happened after the request arrived. In affected versions, the handler could process a supported event before establishing that PayPal was actually the sender. In my local lab, a forged event could change the state of a matching payment record.
The expected order is:
- Authenticate the sender
- Validate the event
- Change payment state
The affected flow effectively performed steps 2 and 3 without first completing step 1. The issue was fixed in WPForms 1.10.0.5 and is tracked as CVE-2026-4986.
Then came the part I found more interesting: triage told me I was reporter #11. That number does not prove exploitation, and it does not tell us the total number of people who found the vulnerability. It does establish a lower bound: at least eleven researchers independently converged on the same trust failure.
The write up covers:
- the vulnerable code path
- my local reproduction
- why payload validation was not sender authentication
- the fallback listener
- the patch
- why duplicate reports may be useful rediscovery intelligence
Full write-up: https://blog.himanshuanand.com/2026/07/reporter-11-10-people-found-the-wpforms-paypal-bug-before-me-cve-2026-4986/
Testing was limited to my own local environment. I am not claiming original CVE credit; I independently rediscovered and reported the issue. Disclosure: I wrote and performed the research, code review and local reproduction.
I used an AI to help copy edit and organize the final article.
Should duplicate report volume affect how urgently a vendor treats a vulnerability?
[link] [comments]