LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52201: WordPress pTypeConverter Plugin <= 0.2.8.1 is vulnerable to SQL Injection

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Brian D. Goad pTypeConverter.This issue affects pTypeConverter: from n/a through 0.2.8.1.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-52201 is a SQL injection flaw in the WordPress pTypeConverter plugin through version 0.2.8.1. It could let an authenticated attacker affect database-backed site data confidentiality and availability. The source bundle does not name a fixed version, so teams should verify vendor guidance before assuming an upgrade path.

Executive priority

Prioritize this for any WordPress environment using pTypeConverter, especially public sites or sites with many user accounts. The risk is high, but urgency depends on plugin presence and whether a supported fix exists.

Technical view

The issue is CWE-89 SQL injection in Brian D. Goad pTypeConverter for WordPress, affecting versions through 0.2.8.1. CVSS 3.1 is 7.6 high: network reachable, low complexity, no user interaction, high confidentiality impact, low availability impact, changed scope, and high privileges required per the CVE vector.

Likely exposure

Exposure is limited to WordPress sites with pTypeConverter installed, especially versions at or below 0.2.8.1. The bundle does not provide CPEs, install prevalence, vulnerable parameters, or a confirmed fixed release.

Exploitation context

The source bundle says this CVE is not in KEV, and it provides no cited evidence of active exploitation. Patchstack labels it a subscriber SQL injection vulnerability, while the CVSS vector lists high privileges required; treat privilege requirements as advisory data needing validation.

Researcher notes

Evidence is sparse: the bundle provides CVSS, CWE, affected plugin range, and Patchstack reference, but not request vectors, vulnerable code paths, proof-of-concept status, or fixed release. Do not infer exploitation or affected forks without additional public vendor data.

Mitigation direction

  • Inventory WordPress sites for pTypeConverter and record installed versions.
  • Check Patchstack and vendor guidance for a fixed version or official workaround.
  • Disable or remove the plugin if it is unnecessary or unsupported.
  • Restrict administrative access and review WordPress account hygiene.
  • Ensure database backups and restoration procedures are current.

Validation and detection

  • Confirm whether pTypeConverter is installed and active on each WordPress instance.
  • Compare installed versions against the affected range through 0.2.8.1.
  • Review advisory updates for privilege requirement and fixed-version clarification.
  • Check web and database logs for suspicious plugin-related errors or unusual authenticated activity.
  • Verify least-privilege database permissions for the WordPress application account.
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-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-52201 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
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/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
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L2.34.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2023-52201Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/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
Brian D. GoadpTypeConverterptypeconverter, n/aunaffected
Weakness

CWE details

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