Taxonomy FilterWordPress extension · Andrealandonio
CVE-2023-48282
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 Andrea Landonio Taxonomy filter allows Cross Site Request Forgery.This issue affects Taxonomy filter: from n/a through 2.2.9.
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 Taxonomy filter plugin by Andrea Landonio (versions through 2.2.9) allows remote attackers to perform unauthorized state-changing actions on behalf of authenticated users by tricking them into visiting malicious pages.
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
Taxonomy FilterWordPress extension
<= 2.2.9CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 the Taxonomy Filter plugin is installedCheck your WordPress plugins directory or the WordPress admin panel under Plugins to confirm the 'Andrealandonio Taxonomy Filter' plugin is active on your siteAffected if the plugin is installed and active
-
Determine the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and look for the Taxonomy Filter plugin version number, or check the plugin header in its main PHP fileAffected if the version is 2.2.9 or lower
-
Inspect forms for nonce token fieldsView the source of any frontend or admin forms generated by the Taxonomy Filter plugin. Look for input fields named '_wpnonce' or similar nonce tokens in form markupAffected if forms lack nonce token fields entirely or have them missing from state-changing form submissions
-
Check AJAX action handlers for nonce verificationExamine the plugin PHP files for AJAX handlers (wp_ajax_* and wp_ajax_nopriv_* hooks). Verify that each handler includes wp_verify_nonce() or check_ajax_referer() calls before processing requestsAffected if AJAX handlers process requests without validating nonce tokens
-
Test for CSRF vulnerability in filter actionsAttempt a filtered request (such as applying a taxonomy filter) from an unauthenticated or external context. If the filter state changes without a nonce validation error, the vulnerability is presentAffected if state-changing filter operations succeed without valid nonce verification
You are affected if the Andrealandonio Taxonomy Filter plugin version is 2.2.9 or lower and forms or AJAX actions lack proper nonce validation for state-changing 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 tokens on all state-changing operations (forms and AJAX actions) and validate these nonces server-side before processing requests.
Fix this in Taxonomy Filter
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-48282 — 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-48282 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