LiveActive security incident?Get immediate response
CVE Record

CVE-2023-38382: WordPress Subscribe to Category Plugin <= 2.7.4 is vulnerable to SQL Injection

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Daniel Söderström / Sidney van de Stouwe Subscribe to Category allows SQL Injection.This issue affects Subscribe to Category: from n/a through 2.7.4.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-38382 is a reported SQL injection issue in the WordPress Subscribe to Category plugin up to version 2.7.4. SQL injection can put site data at risk, but the provided sources do not include a CVSS score, fixed version, exploitation evidence, or attack prerequisites.

Executive priority

Prioritize discovery first. If the plugin is present on public or data-sensitive WordPress sites, treat remediation as time-sensitive because SQL injection can affect confidentiality and integrity. If the plugin is absent, no action is needed beyond documentation.

Technical view

The CVE maps to CWE-89: improper neutralization of SQL command elements. The affected product is Subscribe to Category, package slug subscribe-to-category, through 2.7.4. Sources do not describe the vulnerable parameter, authentication requirement, exploitability, impact scope, or remediation release.

Likely exposure

Exposure is limited to WordPress sites with the Subscribe to Category plugin installed at version 2.7.4 or earlier. No CPEs are provided, so asset checks should use WordPress plugin inventory, plugin slug, and installed version.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat this as a credible SQL injection report with incomplete public detail, not as confirmed exploitation in the wild.

Researcher notes

Public evidence is sparse. Do not assume unauthenticated access, exploit maturity, or a specific fix from the provided sources. Research should focus on confirming installation, version, reachable plugin surfaces, and vendor remediation status without weaponized testing.

Mitigation direction

  • Inventory WordPress sites for the subscribe-to-category plugin and version.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed release.
  • Update if a trusted fixed version is available.
  • Disable or remove the plugin if no safe version can be confirmed.
  • Review compensating controls for WordPress database and admin access.

Validation and detection

  • Confirm whether Subscribe to Category is installed on each WordPress site.
  • Record exact plugin versions and flag 2.7.4 or earlier.
  • Check whether affected sites expose plugin subscription functionality publicly.
  • Review web and database logs for unusual SQL errors tied to plugin requests.
  • Verify any update or removal in staging before production rollout.
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-38382 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Daniel Söderström / Sidney van de StouweSubscribe to Categorysubscribe-to-category, n/aunaffected
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.