CVE-2023-40198
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Antsanchez Easy Cookie Law plugin <= 3.1 versions.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Easy Cookie Law WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions (such as modifying plugin settings) by crafting malicious requests that the user's browser automatically submits due to missing anti-CSRF token validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 3.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Easy Cookie Law plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Antsanchez Easy Cookie Law' or 'Easy Cookie Law', or check the /wp-content/plugins/ directory for a folder containing 'easy-cookie-law' or similarAffected if plugin is present in the WordPress installation
-
Identify installed plugin versionIn Plugins page, click 'View Details' on the Easy Cookie Law plugin, or open the main plugin PHP file and look for the 'Version' header in the plugin comment blockAffected if version number is 3.1 or lower
-
Verify plugin settings are accessibleAs an administrator, navigate to the plugin settings page (usually under Settings > Easy Cookie Law or a dedicated admin menu item created by the plugin)Affected if plugin settings page loads and accepts admin input
If Easy Cookie Law plugin is installed at version 3.1 or lower and has an accessible admin settings page, the site is vulnerable to CSRF attacks on administrative actions.
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 · scopedImplement WordPress nonces (anti-CSRF tokens) for all state-changing operations including form submissions and AJAX requests, and verify the nonce before processing any administrative action.
Upgrade to Easy Cookie Law version 3.2 or later (the first fixed release)
- 1. Backup your WordPress site and database before making any changes
- 2. Navigate to the WordPress admin dashboard
- 3. Go to Plugins > Installed Plugins
- 4. Find 'Easy Cookie Law' by Antsanchez
- 5. If an update is available, click 'Update Now' to install the latest version
- 6. Verify the update was successful by checking the plugin version number
- 7. Test the plugin functionality to ensure the cookie consent features work correctly
- 8. If no update is available in your admin, manually download the latest version from the WordPress Plugin Directory and upload via Plugins > Add New > Upload Plugin
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-40198 — 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-2023-40198 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