LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52225: WordPress Taggbox Plugin <= 3.1 is vulnerable to PHP Object Injection

Deserialization of Untrusted Data vulnerability in Tagbox Tagbox – UGC Galleries, Social Media Widgets, User Reviews & Analytics.This issue affects Tagbox – UGC Galleries, Social Media Widgets, User Reviews & Analytics: from n/a through 3.1.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-52225 is a critical vulnerability in the WordPress Tagbox/Taggbox widget plugin through version 3.1. It may let an unauthenticated attacker abuse unsafe PHP object deserialization. For organizations running this plugin on public WordPress sites, treat this as urgent because the CVSS rating indicates potential full confidentiality, integrity, and availability impact.

Executive priority

High priority for any organization using this plugin on internet-facing WordPress sites. The vulnerability is rated CVSS 10.0 and requires no authentication. If the plugin is not present, no action is needed beyond documenting non-exposure.

Technical view

The issue is CWE-502, Deserialization of Untrusted Data, in taggbox-widget/Tagbox UGC Galleries, Social Media Widgets, User Reviews & Analytics through 3.1. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, scoring 10.0. The provided sources do not name a patched version or specific mitigation.

Likely exposure

Exposure is likely limited to WordPress sites with the Tagbox/Taggbox widget plugin installed at version 3.1 or earlier. Publicly reachable WordPress sites would be most exposed because the CVSS vector indicates network access and no authentication required.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The unauthenticated, network-reachable CVSS profile makes exploitation risk serious if vulnerable installations exist, but exploit availability and real-world use are not established by the provided sources.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The bundle identifies the bug class and affected range through 3.1, but does not provide root-cause details, proof of concept status, exploit telemetry, or a named fixed version. Avoid assuming broader Tagbox products are affected.

Mitigation direction

  • Inventory WordPress sites for the taggbox-widget plugin.
  • Identify installed plugin versions and flag version 3.1 or earlier.
  • Check vendor or Patchstack guidance for a fixed version or recommended action.
  • Disable or remove the plugin where business impact allows until guidance is confirmed.
  • Prioritize public-facing WordPress sites for review first.

Validation and detection

  • Confirm plugin presence from WordPress admin or asset inventory.
  • Record the exact installed plugin version.
  • Compare findings against CVE-2023-52225 and Patchstack advisory details.
  • Review web logs for suspicious unauthenticated requests to WordPress plugin paths.
  • Document whether the plugin was removed, disabled, or updated.
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-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-52225 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
Critical
CVSS
10 (3.1)
Known Exploited
No
Published

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

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
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2023-52225Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
TagboxTagbox – UGC Galleries, Social Media Widgets, User Reviews & Analyticstaggbox-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-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.