dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-5229

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Form Notify WordPress plugin fails to validate that a LINE OAuth user matches the WordPress account they're attempting to access. When LINE doesn't return an email, the plugin trusts the 'form_notify_line_email' cookie—which an attacker can control—to select the WordPress user to authenticate, allowing complete account takeover of any user including administrators.

MitigationUpdate to version 1.1.11 or later which removes the vulnerable cookie-based authentication fallback. If no update is available, disable the plugin until a patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Form Notify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Form Notify' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active, making the vulnerability potentially exploitable.
  2. Check the installed version
    On the Plugins page, find Form Notify and view the version number displayed below the plugin name. Compare this to version 1.1.11.
    Affected if The installed version is earlier than 1.1.11, indicating the vulnerable code is present.
  3. Inspect plugin for cookie-based authentication code
    Access the plugin files via FTP or file manager. Examine the main plugin PHP file (usually form-notify.php or similar) for occurrences of 'form_notify_line_email' and look for code that uses this cookie value to authenticate users without proper validation.
    Affected if Code exists that reads the 'form_notify_line_email' cookie and uses it for authentication without verifying it against the LINE OAuth response.
  4. Check if LINE OAuth email retrieval is enabled
    Review the plugin settings in WordPress admin under Form Notify configuration. Determine whether the plugin is configured to request and use email from LINE OAuth, or if it falls back to cookie-based authentication.
    Affected if The plugin is configured to allow authentication without requiring email from LINE, relying on the vulnerable cookie fallback mechanism.

A user is affected if the Form Notify plugin is active, installed at a version before 1.1.11, and the vulnerable cookie-based authentication code is present and functional.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Update to version 1.1.11 or later which removes the vulnerable cookie-based authentication fallback. If no update is available, disable the plugin until a patch is released.

Recommended fix Moderate confidence

1.1.11 or latest stable release

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Form Notify plugin
  4. Check the current version is 1.1.10 or below
  5. Update the plugin to the latest available version (1.1.11 or higher) which contains the security fix
  6. Alternatively, download the fixed version from the WordPress plugin repository or GitHub and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5229 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data