Public proof of concept

CVE-2026-5229

A public proof of concept exists; no exploitation attested.

Published2026-05-15
WeaknessCWE-287

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The Form Notify plugin for WordPress is vulnerable to Authentication Bypass in versions up to and including 1.1.10. This is due to the plugin trusting user-controlled cookie data to determine which WordPress account to authenticate after a LINE OAuth login. When LINE doesn't provide an email address (which is common), the plugin falls back to reading the 'form_notify_line_email' cookie value without verifying that the LINE account is associated with that email address. This makes it possible for unauthenticated attackers to gain access to any user account on the site, including administrator accounts, by completing a LINE OAuth flow with their own LINE account while injecting a malicious cookie containing the target victim's email address.

Timeline

dates in UTC

2026-05-1509:16CVE publishedNVD
2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-5229?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-5229?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-5229 yet.

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

read 2026-10-23 19:25 UTC

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: 1 repository, unverifiedxxconi/CVE-2026-5229

Sources

NVDCVE recordread 2026-10-23
CISA-ADPSSVC decisionnone2026-05-15
OpenCVESSVC decisionnone—
CNACVSS 3.19.8read 2026-10-23
CNAweakness (CWE)CWE-287read 2026-10-23
FIRST EPSSEPSS score1.1 %2026-10-23
PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published: 2026-05-15
Last Modified: 2026-06-17
NVD status: Deferred

Frequently asked questions

What is CVE-2026-5229?

Is CVE-2026-5229 actively exploited?

Active exploitation of CVE-2026-5229 has not been confirmed. Its EPSS score was 1.1% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-5229?

CVE-2026-5229 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database