LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52204: WordPress Randomize Plugin <= 1.4.3 is vulnerable to SQL Injection

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Javik Randomize.This issue affects Randomize: from n/a through 1.4.3.

HighCVSS 8.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Randomize, a WordPress plugin by Javik, is reported vulnerable to SQL injection through version 1.4.3. A low-privileged authenticated user could potentially cause database queries to expose sensitive data and affect availability. This matters most for WordPress sites that allow contributor-level access or have many user accounts.

Executive priority

Prioritize remediation for public WordPress sites with multiple contributors, customer data, or sensitive content. The main business concern is possible database disclosure from a high-severity plugin flaw, but current sources do not prove active exploitation.

Technical view

CVE-2023-52204 is a CWE-89 SQL injection in Javik Randomize through 1.4.3. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L, scoring 8.5. Sources indicate contributor-level privilege is relevant, with high confidentiality impact and low availability impact.

Likely exposure

Exposure appears limited to WordPress sites running the Randomize plugin at version 1.4.3 or earlier, especially where contributor or other low-privileged authenticated accounts exist. The bundle does not identify affected CPEs or a confirmed fixed version.

Exploitation context

The provided bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates network reachability, low attack complexity, no user interaction, and required low privileges. Do not treat this as unauthenticated exploitation based on the available evidence.

Researcher notes

Evidence is sparse beyond the CVE metadata and Patchstack entry. The affected range is through 1.4.3, with PR:L and no UI required. Avoid assuming unauthenticated reachability, exploit availability, or a fixed version unless confirmed by vendor or advisory updates.

Mitigation direction

  • Inventory WordPress sites for the Javik Randomize plugin and installed version.
  • Check vendor, WordPress, or Patchstack guidance for a fixed release or official workaround.
  • If no fixed version is available, disable or remove the plugin where business risk allows.
  • Restrict contributor-level access and remove unnecessary WordPress accounts.
  • Monitor WordPress and database logs for unusual plugin-related requests or query errors.

Validation and detection

  • Confirm whether Randomize is installed and whether its version is 1.4.3 or earlier.
  • Review user roles for contributor or other low-privileged authenticated access.
  • Verify remediation by confirming the plugin is removed, disabled, or updated per vendor guidance.
  • Check security monitoring for suspicious database errors or access patterns around affected sites.
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-52204 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
8.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
JavikRandomizerandomize, n/aunaffected
Weakness

CWE details

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