Skip to content
Fencer Intel
no cvss —

CVE-2026-130891 json

Newsletter < 9.4.0 - Unauthenticated Private Newsletter Disclosure via Subscriber Email

published 22h ago modified 22h ago also EUVD-2026-132005

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

The Newsletter WordPress plugin before 9.4.0 does not check that a visitor is really the subscriber before showing them newsletters marked as private, and accepts a weaker subscriber identifier that anyone can obtain by submitting a known subscriber's email address to the public subscription form, allowing unauthenticated attackers who know a subscriber's email address to read every private newsletter sent to that subscriber.

Patch / fix

  • Unknown Newsletter 9.4.0

Is CVE-2026-130891 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

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-21).

Exploits and checks

  • wpscan.com https://wpscan.com/vulnerability/f54596fc-4247-4f91-a80a-c74f55b7b41f/ referenced PoC, tagged "exploit" by a source, unverified

Affected products

  • Unknown Newsletter

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Technology feeds

References

Sources

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.