CVE-2025-24571
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 · uneditedMissing Authorization vulnerability in Epsiloncool WP Fast Total Search fulltext-search allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Fast Total Search: from n/a through <= 1.78.258.
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 confidenceMissing authorization vulnerability in the WP Fast Total Search WordPress plugin allows attackers to exploit incorrectly configured access control security levels. This broken access control issue enables unauthorized access to search functionality that should be restricted based on user permissions.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 WP Fast Total Search versionIn WordPress admin, go to Plugins > Installed Plugins > WP Fast Total Search and note the version number displayedAffected if Version is older than the version that includes the security fix (compare against the vendor's security release)
-
Verify search endpoint accessibilityAttempt to access the plugin's search functionality via its AJAX endpoint or search URL without logging in or with a low-privilege user accountAffected if Search results are returned without requiring proper authentication or appropriate user permissions
-
Inspect user role capabilitiesCheck WordPress user roles and their capabilities for search-related actions in the plugin settings (if available in admin panel) or via WP-CLI role commandsAffected if Lower-privileged users (e.g., subscribers) can access search functionality that should be restricted to administrators or higher roles
-
Test cross-user data accessUsing a low-privilege user account, attempt to search for or retrieve content that should only be accessible to administrators or specific user rolesAffected if Sensitive or restricted content is returned in search results to unauthorized users
If the plugin version is unpatched AND search functionality is accessible to unauthorized users, the environment is affected by this CVE.
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.
dbcve · scopedUpdate WP Fast Total Search to the latest version once released by the vendor and audit user role permissions for search functionality to ensure proper access controls are enforced.
Latest version of WP Fast Total Search (verify version > 1.78.258 after update)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate WP Fast Total Search (WP Fast Total Search) by Epsiloncool
- 4. Check the current version number displayed
- 5. If version is <= 1.78.258, update the plugin to the latest available version
- 6. After update, verify the plugin is running on a version newer than 1.78.258
- 7. Test that the authorization controls are functioning correctly for search functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24571 — 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-24571 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