Loading vulnerability…
CVE-2026-14840 is an access control and trust-boundary flaw in the YOP Poll WordPress plugin before version 7.0.6. The plugin enforces a per-IP voting restriction for public polls, but it does not validate the actual client source address and instead relies on client-controlled forwarding headers to determine voter identity. Because these headers can be spoofed by a direct client unless they are sanitized and set only by a trusted intermediary, an unauthenticated attacker can supply arbitrary values to appear as different source IPs and repeatedly bypass the plugin's per-IP vote limit. The issue affects poll integrity rather than the underlying WordPress host.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small standalone exploit PoC for CVE-2026-14840 affecting the YOP Poll WordPress plugin before version 7.0.6. The core exploit is in cve_2026_14840_poc.py, a Python script that fetches a public page containing a YOP Poll, parses embedded JSON initialization data to recover poll_id, nonce, answer identifiers, and page_id, then repeatedly submits vote requests to the plugin REST API. Its main capability is bypassing the plugin’s one-vote-per-IP restriction by setting a different spoofed X-Forwarded-For value on each request. The script first tries /wp-json/yop-poll/v1/votes and falls back to /?rest_route=/yop-poll/v1/votes for plain permalink WordPress installations. Success is determined by HTTP status and JSON response content indicating a recorded vote. This is an application-layer web exploit, not an RCE or shell payload. Repository structure is straightforward: README.md documents the vulnerability, usage, and lab workflow; cve_2026_14840_poc.py is the main exploit entry point; requirements.txt lists Python dependencies (requests and urllib3); lab/docker-compose.yml provisions a local WordPress + MySQL + wpcli environment; and lab/setup.php seeds the lab by creating a vulnerable poll and a public page containing the poll shortcode. The lab files are for reproducible validation only and do not add offensive capability beyond setting up a target environment. The exploit is operational rather than a mere detector because it actively casts votes and can alter poll results if the target is vulnerable. It requires no authentication, assuming the poll is public and the vulnerable plugin behavior is present.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.