Recent Posts SliderWordPress extension · Recent Posts Slider Project
CVE-2023-35778
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 Neha Goel Recent Posts Slider plugin <= 1.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 Neha Goel Recent Posts Slider WordPress plugin version 1.1 and below allows attackers to trick authenticated administrators into performing unintended actions, such as modifying plugin settings or manipulating slider configurations, by forging malicious requests.
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
Recent Posts SliderWordPress extension
<= 1.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.
-
Verify Recent Posts Slider plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Recent Posts Slider' or inspect the plugin directory at wp-content/plugins/recent-posts-slider/ and check the main PHP file for the version headerAffected if The plugin is installed and its version is 1.1 or lower
-
Check plugin version numberOpen the main plugin file (usually recent-posts-slider.php) and locate the Version header in the plugin comment block, or check the version in WordPress plugin admin panelAffected if Version is 1.1 or below (any version <= 1.1)
-
Inspect forms for nonce fieldsNavigate to the plugin settings page (usually under Settings > Recent Posts Slider) and view the page source (right-click > View Page Source) to check if HTML forms contain input fields with names like '_wpnonce' or 'nonce'Affected if Forms do not contain any nonce input fields (the absence of _wpnonce indicates no CSRF protection)
-
Check AJAX actions for nonce verificationExamine the plugin PHP files for AJAX handlers (wp_ajax_ and wp_ajax_nopriv_ hooks) and verify if they call wp_verify_nonce() or check_admin_referer() before processing requestsAffected if AJAX actions lack nonce verification code (no wp_verify_nonce or check_admin_referer calls)
-
Verify state-changing operations lack protectionReview plugin code for any $_POST, $_GET, or $_REQUEST handling that modifies settings or slider configurations without nonce validationAffected if Settings/slider configuration changes can be triggered without a valid nonce token
A user is affected if the Recent Posts Slider plugin version 1.1 or lower is installed AND the plugin's forms or AJAX actions lack WordPress nonce validation for CSRF protection.
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 dataImplement anti-CSRF tokens (WordPress nonces) on all state-changing forms and AJAX actions within the plugin, and validate the nonce on the server side before processing any request.
Fix this in Recent Posts Slider
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35778 — 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-35778 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