NVD / CVE Program· CNA WPScan

CVE-2023-6620: Post SMTP < 2.8.7 - Admin+ SQL Injection

Noroxi assessment

Priority: Monitor (action score 32/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 14% (FIRST EPSS); higher than 96.5% of all records.
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Unknown POST SMTP Mailer 2.8.7.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Unknown POST SMTP Mailer 2.8.7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The POST SMTP Mailer WordPress plugin before 2.8.7 does not properly sanitise and escape several parameters before using them in SQL statements, leading to a SQL injection exploitable by high privilege users such as admin.

HighCVSS 7.2 · v3.1—No exploit Fix available

SQL injection

Published: Jan 15, 2024
Updated: Jun 17, 2026
EPSS: 14.0% · 96th percentile
CWE: CWE-89

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 4 / 30 · 14.0%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Is Post SMTP – Complete Email Delivery and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App on your site?

WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
wpexperts	post smtp	cpe:2.3:a:wpexperts:post_smtp

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

wpexperts post smtpbefore 2.8.7

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.

Unknown POST SMTP Mailer
- before 2.8.7affected · semver

Same product

wpexperts: all records

Other highest-scoring records for the same primary product.

CVE-2023-6875POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress <= 2.8.7 - Authorization Bypass via type connect-app API
66This week
CVE-2023-52233WordPress POST SMTP Mailer plugin <= 2.8.6 - Broken Access Control on API vulnerability
39Monitor
CVE-2025-22800WordPress Post SMTP plugin <= 2.9.11 - Broken Access Control vulnerability
35Monitor

Published before and after this one in the same product

← EarlierCVE-2023-7027Jan 3, 2024 · POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress <= 2.8.7 - Unauthenticated Stored Cross-Site Scripting via device
21Monitor
← EarlierCVE-2023-6621Jan 3, 2024 · Post SMTP < 2.8.7 - Reflected Cross-Site Scripting
24Monitor
Later →CVE-2023-3178Jan 16, 2024 · POST SMTP Mailer < 2.5.7 - Arbitrary Log Deletion via CSRF
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Unknown POST SMTP Mailer	2.8.7	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Alex Sanfordfinder
WPScancoordinator

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-5207136 days apartPOST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress <= 2.9.3 - Authenticated (Administrator+) SQL Injection
28Monitor
CVE-2024-52436308 days apartWordPress Post SMTP plugin <= 2.9.9 - SQL Injection vulnerability
28Monitor
CVE-2024-13844418 days apartPost SMTP <= 3.1.2 - Authenticated (Administrator+) SQL Injection via columns Parameter
19Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0034 · Jan 16, 2024(WordPress Eklenti Zafiyeti)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

The bug in code

The whole CWE-89 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = '" + owner + "'"
4);

Fixed

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = $1",
4  [owner]
5);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

All records