LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48282: WordPress Taxonomy filter Plugin <= 2.2.9 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-48282 is a CSRF flaw in the WordPress Taxonomy filter plugin through version 2.2.9. An attacker may trick an authenticated user into causing unwanted plugin-related changes. The cited data rates impact as medium: no confidentiality impact, low integrity impact, and low availability impact.

Executive priority

Treat this as a moderate-priority WordPress plugin issue. It is not evidenced as actively exploited in the supplied sources, but affected sites should be inventoried and remediated through normal vulnerability management, with faster action for high-value or frequently administered sites.

Technical view

The vulnerability is CWE-352 Cross-Site Request Forgery in Andrea Landonio Taxonomy filter for WordPress, affecting versions through 2.2.9. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites running the Taxonomy filter plugin at affected versions through 2.2.9. Practical risk depends on authenticated users being induced to interact with malicious content while logged in. The bundle does not identify affected configurations beyond the plugin and version range.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. CSRF generally depends on a victim user action and an authenticated browser session. No exploit maturity details are provided in the supplied sources.

Researcher notes

Evidence is sparse. The supplied CVE data identifies CSRF, version range, CVSS, CWE-352, and a Patchstack entry, but does not include request details, affected endpoints, proof of exploitation, or a named fixed version. Avoid assuming impact beyond low integrity and availability effects.

Mitigation direction

  • Inventory WordPress sites for the taxonomy-filter plugin and version.
  • Check vendor, WordPress, or Patchstack guidance for fixed versions or mitigations.
  • Update the plugin if a fixed release is available from trusted sources.
  • Disable or remove the plugin where it is unnecessary or unsupported.
  • Prioritize sites with active administrators and business-critical content workflows.

Validation and detection

  • Confirm whether taxonomy-filter is installed on each WordPress site.
  • Verify installed plugin versions against the affected range through 2.2.9.
  • Review administrative change logs for unexpected taxonomy or plugin-related changes.
  • Check whether compensating controls restrict untrusted links for authenticated administrators.
  • Document remediation status for each affected site.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-48282 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-48282Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Andrea LandonioTaxonomy filtertaxonomy-filter, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.