CVE-2025-60170
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 Taraprasad Swain HTACCESS IP Blocker htaccess-ip-blocker allows Stored XSS.This issue affects HTACCESS IP Blocker: from n/a through <= 1.0.
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 confidenceA CSRF vulnerability in the HTACCESS IP Blocker plugin allows authenticated administrators to be tricked into submitting malicious requests that inject XSS payloads (Stored XSS) into IP blocking rules. When other administrators view the IP blocklist, the stored JavaScript executes in their browsers.
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.
-
Identify if HTACCESS IP Blocker plugin is installedCheck your WordPress plugins directory or admin panel for 'HTACCESS IP Blocker' and note the installed version numberAffected if The plugin is installed and running without having been patched to include CSRF nonce verification
-
Examine IP blocking rules for stored XSS payloadsAccess the plugin's IP blocklist admin page and inspect all existing IP blocking rules for suspicious JavaScript tags, event handlers, or encoded payloads in the IP address or hostname fieldsAffected if Any IP blocking rule contains XSS payloads such as <script> tags, javascript: URLs, or event handler attributes like onload/onerror
-
Check plugin source code for anti-CSRF nonce verificationLocate the plugin PHP files (typically in wp-content/plugins/htaccess-ip-blocker) and search for 'wp_verify_nonce' or 'check_admin_referer' calls around state-changing functions that add or edit IP rulesAffected if The plugin lacks nonce verification functions in the code that handles adding or editing IP blocking rules
-
Verify output encoding in admin interface displayReview the plugin code that renders IP addresses and hostnames in the admin blocklist view; check if output functions like esc_html or esc_attr are used when displaying user-supplied IP/hostname dataAffected if User-supplied IP addresses and hostnames are displayed without proper sanitization or encoding in the admin interface
You are affected if the HTACCESS IP Blocker plugin is installed and either the IP blocklist contains suspicious XSS payloads OR the plugin code lacks anti-CSRF nonce verification for IP rule operations.
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 nonce verification for all state-changing operations (adding/editing IP rules) and apply proper output encoding when displaying user-supplied IP addresses or hostnames in the admin interface.
- 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-2025-60170 — 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-60170 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