Kodex Posts LikesWordPress extension · Pierros
CVE-2022-46814
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 Pierre Lebedel Kodex Posts likes plugin <= 2.4.3 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 confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in the Kodex Posts likes WordPress plugin. Attackers can craft malicious requests that trick authenticated administrators or users into performing unwanted actions (such as liking/unliking posts) without their consent, due to missing or insufficient CSRF protections on the plugin's action endpoints.
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
Kodex Posts LikesWordPress extension
<= 2.4.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm Kodex Posts Likes plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Kodex Posts Likes' or 'Pierros Kodex Posts Likes' in the list. Note whether it is activated.Affected if The plugin appears in the installed plugins list and is activated
-
Identify the installed versionClick on the plugin name in the Plugins list to view its details, or check the plugin's main PHP file (typically in wp-content/plugins/kodex-posts-likes/) for a version comment or defined version constant. Compare against the affected range: <= 2.4.3Affected if The installed version number is 2.4.3 or lower, or no version number is displayed (older unversioned release)
-
Inspect plugin action handlers for CSRF protectionLocate the main plugin PHP file(s) in wp-content/plugins/kodex-posts-likes/. Search for action handlers that process like/unlike requests (look for functions handling 'like', 'unlike', or AJAX endpoints). Check if these handlers include nonce verification calls such as wp_verify_nonce, check_admin_referer, or wp_nonce_field before processing the request.Affected if The like/unlike action handlers process requests without verifying a nonce token or CSRF protection is absent from the code
-
Check form submissions and AJAX actions for nonce fieldsIf the plugin includes frontend forms or AJAX functionality for liking/unliking posts, inspect the relevant PHP files to see if nonce fields are generated (wp_nonce_field) when outputting the forms, and if these nonces are validated on submission. Also check any JavaScript files that may handle AJAX requests for nonce inclusion.Affected if Forms or AJAX actions that trigger like/unlike functionality do not include nonce tokens, or the submitted nonces are not validated server-side
A user is affected if the Kodex Posts Likes plugin version is 2.4.3 or lower AND the plugin's like/unlike functionality processes requests without CSRF token validation.
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 dataUpdate the Kodex Posts likes plugin to the latest version which should contain CSRF protection. If no update is available, implement WordPress nonces (wp_nonce_field, check_admin_referer, wp_verify_nonce) on all form submissions and AJAX actions within the plugin.
Fix this in Kodex Posts Likes
Scoped from the published advisory
- 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-2022-46814 — 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-2022-46814 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