CVE-2024-11118
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 404 Error Monitor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1. This is due to missing or incorrect nonce validation on the updatePluginSettings() function. This makes it possible for unauthenticated attackers to make changes to plugin settings and clear up all the error logs via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 404 Error Monitor WordPress plugin lacks nonce validation on its updatePluginSettings() function, allowing unauthenticated attackers to forge administrative requests. This enables modification of plugin settings and deletion of error logs through social engineering (tricking admins to click malicious links).
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
-
Confirm 404 Error Monitor plugin is installedNavigate to WordPress admin > Plugins and look for '404 Error Monitor' in the installed plugins list, or inspect the filesystem at wp-content/plugins/ for a directory named '404-error-monitor' or similarAffected if Plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin > Plugins > 404 Error Monitor, click 'View Details' to display the version number, or read the main plugin PHP file header for the Version fieldAffected if Version cannot be determined or matches any unpatched release of the plugin
-
Verify the plugin is activeCheck the Plugins admin page to see if 404 Error Monitor shows as 'Active' under the plugin statusAffected if Plugin is active and reachable via the WordPress admin interface
-
Check for exposure to administrative actionsInspect the plugin source code for the updatePluginSettings() function and verify whether nonce validation (check_admin_referer, wp_verify_nonce, or similar) is present before processing settings changesAffected if No nonce validation is found in the updatePluginSettings() function, allowing CSRF attacks
-
Confirm admin session exposureDetermine whether administrators in your environment frequently access the WordPress admin panel and could be targeted by social engineering via malicious linksAffected if Admin users click untrusted links while authenticated to WordPress
You are affected if the 404 Error Monitor plugin is installed and active without nonce protection on its updatePluginSettings() function, enabling CSRF attacks via social engineering.
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.
From vendor dataApply vendor patch when released; until then, adminstrators should avoid clicking untrusted links and consider disabling the plugin to prevent CSRF attacks.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11118 — 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-11118 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