CVE-2026-19782Disclosure

LOWCVSS 5.4 · MEDIUM

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

The WPS Bidouille WordPress plugin before 1.33.5 does not have proper authorisation checks in an AJAX action, allowing any authenticated user, such as a subscriber, to retrieve the email addresses of all registered users.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-200

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 2 mentions across 1 observed day

What's happening

  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • 2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-08-19: 2Technical Details · 2026-08-19: 208-19
Signal classification1 categories
Disclosure
2100.0%
Referenced assets2 URLs
By indicator
Full discourse2 posts
  • Infoflowcloud@infoflowcloud
    Disclosure

    🚨*CVE* CVE-2026-19782 The WPS Bidouille WordPress plugin before 1.33.5 does not have proper authorisation checks in an AJAX action, allowing any authenticated user, such as a subscriber, t… https://www.cve.org/CVERecord?id=CVE-2026-19782 ----- Traducción: CVE-2026-19782 El … https://infoflow.cloud`

    Post summary

    The tweet announces CVE‑2026‑19782, noting an authorization bypass in WPS Bidouille’s AJAX action for authenticated users, but provides no PoC, exploit, or patch details.

    00000104
    100 followersView on X
  • CVE@CVEnew
    Disclosure

    CVE-2026-19782 The WPS Bidouille WordPress plugin before 1.33.5 does not have proper authorisation checks in an AJAX action, allowing any authenticated user, such as a subscriber, t… https://www.cve.org/CVERecord?id=CVE-2026-19782

    Post summary

    The CVE highlights an authorization bypass in the WPS Bidouille WordPress plugin via an unchecked AJAX action, enabling any authenticated user—such as a subscriber—to exploit the flaw. No exploit code, patch, or evidence of active exploitation is presented.

    00000696
    58.0K followersView on X

Explore more