LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45763: WordPress Taggbox Plugin <= 2.9 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Taggbox plugin <= 2.9 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-45763 affects the WordPress Taggbox plugin up to version 2.9. It is a CSRF issue, meaning an attacker may be able to trick a logged-in site user into making unwanted plugin changes. The impact is limited integrity and availability, not direct data theft, based on the provided CVSS vector.

Executive priority

Treat as a routine but real WordPress hygiene issue. Prioritize internet-facing sites, administrator-heavy environments, and sites where Taggbox controls public content or integrations. It is not supported as actively exploited in the provided sources.

Technical view

The source bundle identifies CWE-352 in Taggbox taggbox-widget for WordPress <=2.9, with CVSS 3.1 score 5.4: network reachable, low complexity, no privileges, user interaction required, unchanged scope, low integrity and availability impact, no confidentiality impact. The exact vulnerable action and fixed version are not provided.

Likely exposure

Exposure is likely limited to WordPress sites that installed the Taggbox plugin at version 2.9 or earlier. The bundle includes inconsistent affected metadata, so teams should verify installed plugin name, slug, and version directly in WordPress inventory.

Exploitation context

The bundle marks this CVE as not in KEV, and no cited source reports active exploitation. CSRF generally depends on a logged-in user visiting attacker-controlled content, so business risk depends on admin usage patterns and the plugin actions exposed without CSRF protection.

Researcher notes

Evidence is sparse. Patchstack is the only vulnerability database reference in the bundle, and no exploit details or fixed version are supplied. Avoid assuming broader Taggbox products are affected beyond the WordPress plugin slug and version range stated in the description.

Mitigation direction

  • Inventory WordPress sites for the Taggbox taggbox-widget plugin.
  • Update the plugin using official WordPress or vendor guidance if available.
  • Disable or remove the plugin where it is not business-critical.
  • Restrict administrative access to trusted users and hardened browsers.
  • Monitor vendor and Patchstack guidance for a named fixed version.

Validation and detection

  • Confirm whether any site runs Taggbox version 2.9 or earlier.
  • Review plugin changelog or vendor advisory for CSRF remediation details.
  • Verify sensitive plugin actions require nonce and permission checks.
  • Check recent WordPress admin activity for unexpected Taggbox configuration changes.
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-45763 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-45763Attack 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
TaggboxTaggboxtaggbox-widget, 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.