CVE-2023-6875

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2024-01-11. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 90%
CISA-KEV: Not listedEPSS: 90%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a type juggling issue on the connect-app REST endpoint in all versions up to, and including, 2.8.7. This makes it possible for unauthenticated attackers to reset the API key used to authenticate to the mailer and view logs, including password reset emails, allowing site takeover. CVE-2023-52233 appears to be a duplicate of this issue.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
95(Track)
EG Risk 95/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation90% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.8%
KEV
Not listed

Published

January 11, 2024

Last Modified

April 8, 2026

References (7)

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:30 UTCEG score recompute
  2. 2026-07-22 23:17 UTCEG score recompute
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-22 14:07 UTCEPSS rescore
  5. 2026-07-15 16:56 UTCEPSS rescore
  6. 2026-07-11 10:41 UTCOSV refresh
  7. 2026-07-08 15:13 UTCEPSS rescore
  8. 2026-07-06 16:26 UTCEPSS rescore
  9. 2026-07-06 16:26 UTCEPSS rescore
  10. 2026-07-05 02:29 UTCEPSS rescore
  11. 2026-06-30 23:21 UTCEPSS rescore
  12. 2026-06-30 23:21 UTCEPSS rescore
  13. 2026-06-29 14:05 UTCEPSS rescore
  14. 2026-06-28 04:55 UTCEPSS rescore
  15. 2026-06-24 14:04 UTCEPSS rescore
  16. 2026-06-24 14:04 UTCEPSS rescore
  17. 2026-06-23 21:31 UTCEPSS rescore
  18. 2026-06-23 21:31 UTCEPSS rescore
  19. 2026-06-22 17:05 UTCOSV refresh
  20. 2026-06-15 17:47 UTCEPSS rescore
  21. 2026-06-12 23:11 UTCEPSS rescore
  22. 2026-06-11 13:59 UTCEPSS rescore
  23. 2026-06-10 22:17 UTCEPSS rescore
  24. 2026-06-10 13:21 UTCEPSS rescore
  25. 2026-06-08 14:16 UTCEPSS rescore
Show 29 more
  1. 2026-06-08 14:16 UTCEPSS rescore
  2. 2026-06-06 13:46 UTCEPSS rescore
  3. 2026-06-06 13:46 UTCEPSS rescore
  4. 2026-06-05 05:09 UTCOSV refresh
  5. 2026-06-04 13:11 UTCEPSS rescore
  6. 2026-06-04 13:11 UTCEPSS rescore
  7. 2026-05-28 13:44 UTCEPSS rescore
  8. 2026-05-28 13:44 UTCEPSS rescore
  9. 2026-05-27 13:40 UTCEPSS rescore
  10. 2026-05-27 13:39 UTCEPSS rescore
  11. 2026-05-26 13:43 UTCEPSS rescore
  12. 2026-05-26 13:43 UTCEPSS rescore
  13. 2026-05-26 07:18 UTCEPSS rescore
  14. 2026-05-26 07:18 UTCEPSS rescore
  15. 2026-05-22 05:06 UTCEG score recompute
  16. 2026-05-22 05:06 UTCGHSA enrichment
  17. 2026-05-20 22:37 UTCEPSS rescore
  18. 2026-05-20 22:37 UTCEPSS rescore
  19. 2026-05-20 22:37 UTCEPSS rescore
  20. 2026-05-20 22:37 UTCEPSS rescore
  21. 2026-05-20 11:21 UTCEPSS rescore
  22. 2026-05-20 11:21 UTCEPSS rescore
  23. 2026-05-20 11:21 UTCEPSS rescore
  24. 2026-05-20 11:21 UTCEPSS rescore
  25. 2026-05-20 11:21 UTCEPSS rescore
  26. 2026-05-18 21:30 UTCEPSS rescore
  27. 2026-05-18 21:30 UTCEPSS rescore
  28. 2026-05-18 21:30 UTCEPSS rescore
  29. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCgbrsh/CVE-2023-6875
    First seen Jan 27, 2024

    Exploit for CVE-2023-6875 - Unauthorized Account Takeover.

    Open source ↗
  • GitHub PoCUlyssesSaicha/CVE-2023-6875
    First seen Jan 13, 2024

    CVE-2023-6875 PoC

    Open source ↗
  • Metasploitauxiliary/admin/http/wp_post_smtp_acct_takeover✓ verified
    First seen Jan 10, 2024

    Wordpress POST SMTP Account Takeover

    Open source ↗
  • Nucleihttp/cves/2023/CVE-2023-6875.yaml
    First seen Jan 1, 2023

    WordPress POST SMTP Mailer <= 2.8.7 - Authorization Bypass

    Open source ↗

Frequently asked(5)

What is CVE-2023-6875?
CVE-2023-6875 is a critical vulnerability published on January 11, 2024. The POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a type juggling issue on the connect-app REST endpoint in all versions up to, and including, 2.8.7.…
When was CVE-2023-6875 disclosed?
CVE-2023-6875 was first published in the National Vulnerability Database on January 11, 2024, with the most recent update on April 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-6875 actively exploited?
CVE-2023-6875 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-6875?
CVE-2023-6875 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-6875?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-6875, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-6875

Explore →

Is Your Infrastructure Affected by CVE-2023-6875?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs