CVE-2026-5229: Receive Notifications After Form Submitting (WordPress plugin) · Improper Authentication
Affects Receive Notifications After Form Submitting (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| m615926Receive Notifications After Form Submitting – Form Notify for Any Forms | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor's advisory channels for updates. Until a fix is released, consider disabling the Form Notify plugin or restricting its use to trusted environments. Avoid relying on LINE OAuth login in this plugin as a sole authentication mechanism.
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/2f0a7d6f-9b95-4052-bab3-85aca01f6ab7?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-notify/trunk/src/APIs/Line/Login/User.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-notify/tags/1.1.08/src/APIs/Line/Login/User.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-notify/trunk/src/APIs/Line/Login/Route.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-notify/tags/1.1.08/src/APIs/Line/Login/Route.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-notify/trunk/src/APIs/Line/Login/User.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-notify/tags/1.1.08/src/APIs/Line/Login/User.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3517908%40form-notify&new=3517908%40form-notify&sfp_email=&sfph_mail= (opens in a new tab)
- github.com/oberonlai/form-notify/commit/5eab0ea (opens in a new tab)
- github.com/oberonlai/form-notify/commit/9780764 (opens in a new tab)