CVE-2025-31779
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 Jonathan Daggerhart Query Wrangler query-wrangler allows Cross Site Request Forgery.This issue affects Query Wrangler: from n/a through <= 1.5.54.
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 Query Wrangler WordPress plugin. The plugin fails to properly validate anti-CSRF tokens (nonces) on state-changing operations, allowing attackers to trick authenticated administrators into performing unintended actions like modifying or deleting queries via crafted links or forms.
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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check if Query Wrangler plugin is installedNavigate to WordPress admin > Plugins and look for 'Query Wrangler', or inspect the /wp-content/plugins/query-wrangler directory existence and read the main plugin file header for version numberAffected if Plugin is installed and version is less than the fixed version (if known) or unpatched
-
Identify state-changing operations in the pluginSearch the plugin source code for handlers that modify data: look for functions handling save, update, delete, or create operations on queries (e.g., save_query, update_query, delete_query, or similar AJAX endpoints)Affected if The plugin handles query modification/deletion without nonce verification
-
Inspect nonce validation in state-changing codeExamine the PHP files handling query modifications. Look for wp_verify_nonce, check_ajax_referer, or wp_create_nonce calls. Verify that nonces are checked BEFORE any database write operationsAffected if State-changing functions lack wp_verify_nonce or check_ajax_referer calls, or nonce checks are missing entirely from POST/GET handlers that modify queries
-
Check for Origin/Referer header validationInspect the same state-changing handlers for server-side validation of $_SERVER['HTTP_ORIGIN'] or $_SERVER['HTTP_REFERER'] to confirm request originAffected if No Origin or Referer header validation is performed on state-changing requests
-
Verify admin action hooks include nonce verificationReview admin_init, admin_post, and AJAX hooks in the plugin. Confirm that any hook triggering query modification calls wp_verify_nonce early in the execution flowAffected if Admin action hooks that modify queries do not verify nonces before processing
The environment is affected if Query Wrangler plugin is installed and its code lacks proper wp_verify_nonce or check_ajax_referer validation on handlers that modify or delete queries.
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 WordPress nonces on all state-changing operations (POST/GET requests that modify data) and verify the nonce before processing. Additionally, check the Origin or Referer header to validate request origin.
- 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-31779 — 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-31779 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