Kebo Twitter FeedWordPress extension · Kebo Twitter Feed Project
CVE-2023-34384
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 Kebo Kebo Twitter Feed plugin <= 1.5.12 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 Kebo Kebo Twitter Feed WordPress plugin affecting versions 1.5.12 and below. The vulnerability likely stems from missing or insufficient anti-CSRF token validation on state-changing operations within the plugin, allowing attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings or feed configurations.
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
Kebo Twitter FeedWordPress extension
<= 1.5.12CVSS 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.
-
Verify Kebo Twitter Feed plugin is installedAccess WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Kebo Twitter Feed' in the list. Alternatively, check the wp-content/plugins/ directory for a folder named 'kebo-twitter-feed' or similar.Affected if The plugin is present in the plugins directory or listed in WordPress admin.
-
Check installed plugin versionIn WordPress admin, find the Kebo Twitter Feed entry in the Plugins list and note the version number displayed below the plugin name. Or open wp-content/plugins/kebo-twitter-feed/readme.txt and check the version line.Affected if The version number is 1.5.12 or lower.
-
Confirm plugin is activeIn WordPress admin > Plugins, verify the Kebo Twitter Feed plugin shows as 'Active' (not just installed but not activated).Affected if The plugin is activated on the WordPress site.
-
Inspect for missing nonce verification in plugin codeExamine the main plugin PHP files (usually kebo-twitter-feed.php or files in includes/ folder) for form submissions and AJAX handlers. Look for the absence of wp_verify_nonce, check_ajax_referer, or nonce_field calls in functions that modify settings or feed configurations.Affected if State-changing functions (settings save, feed config modify) lack nonce verification code.
-
Test for CSRF vulnerability via form inspectionUse browser developer tools to inspect forms generated by the plugin (in admin settings pages). Check if forms contain a hidden input with name '_wpnonce' or 'nonce' and if that nonce is validated server-side when the form is submitted.Affected if Forms lack nonce fields or the nonce field is not validated server-side.
If the Kebo Twitter Feed plugin version 1.5.12 or below is installed and active, and the plugin lacks proper nonce verification in its state-changing operations, the environment is affected by this CSRF vulnerability.
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 Kebo Kebo Twitter Feed plugin to a version newer than 1.5.12, which should include proper nonce verification and CSRF token validation for all forms and AJAX requests. If no update is available, implement manual anti-CSRF protections by adding WordPress nonces to all form submissions and validating them server-side.
Fix this in Kebo Twitter Feed
Scoped from the published advisory
- 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-2023-34384 — 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-34384 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