CVE-2024-6228
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 · uneditedThe Notifications for Forms & WordPress Actions WordPress plugin before 2.6 does not validate a user-supplied value before using it to build a server-side file inclusion path, allowing authenticated users with subscriber-level access and above to include and execute arbitrary local PHP files on the server.
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 confidenceThe Notifications for Forms & WordPress Actions plugin before version 2.6 fails to validate user-supplied input before using it in a server-side file inclusion path, allowing authenticated users with subscriber-level privileges to include and execute arbitrary local PHP files on the server.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionGo to WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Notifications for Forms & WordPress Actions' in the list, and record the version number displayed in the plugin rowAffected if Version is shown as below 2.6 or the version field is missing entirely
-
Confirm plugin is enabledIn the same plugins list, verify the plugin shows an Active status (not Deactivated or Deleted)Affected if Plugin status is Active
-
Identify subscriber-level usersNavigate to WordPress Users menu and review the list of registered users to determine if any accounts with Subscriber role existAffected if One or more Subscriber accounts are present on the site
-
Check for file inclusion functionalityInspect plugin settings or code for any parameter that accepts file paths for inclusion (commonly found in plugin admin pages under Notifications or Actions settings)Affected if The plugin exposes a file inclusion parameter in its configuration interface
The environment is affected if the plugin version is below 2.6, the plugin is active, and at least one Subscriber-level user account exists on the site.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to version 2.6 or later which includes input validation for the file inclusion parameter.
version 2.6
- Backup your WordPress site database and files before making any changes
- Update the 'Notifications for Forms & WordPress Actions' plugin to version 2.6 or later via WordPress admin (Plugins > Updates) or by downloading from wordpress.org
- After updating, verify the plugin is running version 2.6 or higher in Plugins > Installed Plugins
- Test that form notifications and WordPress action triggers continue to function correctly
- Confirm that the vulnerability is patched by attempting the vulnerable parameter (server-side verification only - do not attempt exploitation)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6228 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6228 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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