CVE-2026-5229 json
Receive Notifications After Form Submitting – Form Notify for Any Forms <= 1.1.10 - Unauthenticated Authentication Bypass via LINE OAuth Callback
published 5mo ago modified 4mo ago also EUVD-2026-30516
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2026-5229 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 5mo ago
Exploit prediction
0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- m615926 Receive Notifications After Form Submitting – Form Notify for Any Forms
Classification
- Weakness
-
- CWE-287 Improper Authentication
- Technology feeds
References
- github.com /oberonlai/form-notify/commit/5eab0ea
- github.com /oberonlai/form-notify/commit/9780764
- wordfence.com /threat-intel/vulnerabilities/id/2f0a7d6f-9b95-4052-bab3-85aca01f6ab7?source=cve
- plugins.trac.wordpress.org /browser/form-notify/trunk/src/APIs/Line/Login/User.php#L72
- plugins.trac.wordpress.org /browser/form-notify/tags/1.1.08/src/APIs/Line/Login/User.php#L72
- plugins.trac.wordpress.org /browser/form-notify/trunk/src/APIs/Line/Login/Route.php#L116-L118
- plugins.trac.wordpress.org /browser/form-notify/tags/1.1.08/src/APIs/Line/Login/Route.php#L116-L118
- plugins.trac.wordpress.org /browser/form-notify/trunk/src/APIs/Line/Login/User.php#L53
- plugins.trac.wordpress.org /browser/form-notify/tags/1.1.08/src/APIs/Line/Login/User.php#L53
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3517908%40form-notify&new=3517908%40form-notify&sfp_email=&sfph
Sources
- CVE List CVE-2026-5229
- NVD CVE-2026-5229
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.