CVE-2025-28966
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 dilemma123 Recent Posts Slider Responsive recent-posts-slider-responsive allows Stored XSS.This issue affects Recent Posts Slider Responsive: from n/a through <= 1.0.1.
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 confidenceCSRF vulnerability in the Recent Posts Slider Responsive WordPress plugin (versions <=1.0.1) allows attackers to craft malicious requests that inject stored XSS payloads into the plugin's settings. Missing CSRF protection enables authenticated attackers to trick administrators into submitting crafted forms that persist malicious scripts.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 the plugin is installedNavigate to WordPress admin > Plugins and look for 'Recent Posts Slider Responsive' in the installed plugins list, or check the directory wp-content/plugins/recent-posts-slider-responsive/ exists on the serverAffected if The plugin is present and active on the WordPress site
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Recent Posts Slider Responsive and read the version number from the plugin details; alternatively, check the main plugin PHP file for the 'Version' header in the plugin comment blockAffected if The version is 1.0.1 or lower (any version <=1.0.1)
-
Inspect plugin settings for malicious stored contentAccess the plugin settings page (usually under Settings or a dedicated menu item for 'Recent Posts Slider') and examine all text fields for suspicious JavaScript tags, script elements, event handlers (onclick, onerror, etc.), or encoded payloads; check the database wp_options table for entries related to the plugin (option_name containing 'rpsr' or 'recent_posts_slider')Affected if Any plugin setting contains unsanitized JavaScript code or HTML that could execute in an admin browser
-
Verify CSRF protection is absent in plugin formsExamine the plugin PHP source code for nonce verification: search for 'wp_nonce_field', 'wp_nonce_url', 'check_admin_referer', or 'check_ajax_referer' in all form-handling files within the plugin directory; if these functions are missing from AJAX actions and form processing logic, CSRF protection is not implementedAffected if The plugin forms and AJAX handlers lack nonce verification and referrer checks
A user is affected if the Recent Posts Slider Responsive plugin is installed at version 1.0.1 or lower and its settings contain malicious scripts or its code lacks CSRF nonce 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 nonces/CSRF tokens in all plugin forms and AJAX actions, and apply proper output sanitization and escaping for all user-supplied data before storage and display.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28966 — 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-2025-28966 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