LiveActive security incident?Get immediate response
CVE Record

CVE-2023-26003: WordPress WP Post Corrector <= 1.0.2 - SQL Injection Vulnerability

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in vipul Jariwala WP Post Corrector allows SQL Injection. This issue affects WP Post Corrector: from n/a through 1.0.2.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-26003 is a high-severity SQL injection issue in the WordPress WP Post Corrector plugin through version 1.0.2. It can expose sensitive database data, but the CVSS vector indicates the attacker needs high privileges and no user interaction.

Executive priority

Prioritize identification and removal or mitigation on externally reachable WordPress sites. Treat as urgent where many privileged users exist or administrator accounts are poorly governed.

Technical view

The issue is CWE-89 improper neutralization of SQL command elements in WP Post Corrector. The CVSS v3.1 score is 7.6: network reachable, low complexity, high privileges required, changed scope, high confidentiality impact, no integrity impact, and low availability impact.

Likely exposure

Exposure is limited to WordPress sites running WP Post Corrector through version 1.0.2. The provided data does not identify other affected products, CPEs, or vulnerable components outside the wp-post-corrector plugin.

Exploitation context

The bundle does not cite CISA KEV listing or active exploitation. Risk is still material because SQL injection can disclose database contents, but exploitation appears to require a highly privileged WordPress account based on the CVSS vector.

Researcher notes

Evidence is limited to the CVE record and Patchstack entry. No exploit details, patch version, public exploit status, or vulnerable parameter information is provided in the source bundle.

Mitigation direction

  • Inventory WordPress sites for WP Post Corrector installations.
  • Remove or disable WP Post Corrector where it is not required.
  • If required, check vendor or Patchstack guidance for a fixed release or mitigation.
  • Restrict privileged WordPress access to trusted administrators only.
  • Monitor privileged account activity and database access for anomalies.

Validation and detection

  • Confirm whether wp-post-corrector is installed on each WordPress instance.
  • Record installed plugin versions and flag versions through 1.0.2.
  • Review administrative account access for unexpected or stale privileged users.
  • Check web, application, and database logs for suspicious privileged activity.
  • Track vendor and Patchstack advisories for remediation updates.
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-26003 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-26003Attack 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
vipul JariwalaWP Post Correctorwp-post-corrector, 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.