Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalPublic exploit

Type Juggling Authentication Bypass in Post SMTP WordPress Plugin

IdentifiersCVE-2023-6875CWE-704

CVE-2023-6875 affects the POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin. In all versions up to and including 2.8.7, the plugin contains a type juggling flaw in the connect-app REST endpoint. Due to improper handling of types during authentication or authorization logic, an unauthenticated attacker can reset the API key used by the plugin’s mailer integration and then access protected mail logs. Those logs may contain sensitive email content, including password reset messages. The issue therefore enables both unauthorized data access and unauthorized modification of security-relevant configuration state.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to reset the plugin API key, gain access to email logs, and read sensitive messages processed by the plugin. Where password reset emails are present in the logs, the attacker can use the reset links or tokens to take over WordPress user accounts, including administrative accounts, resulting in full site compromise. The vulnerability also permits unauthorized modification of plugin authentication material, undermining trust in the mailer integration.

Mitigation

If you can’t patch tonight, do this now.

As an interim measure, restrict or block access to the vulnerable connect-app REST endpoint from untrusted networks, including via WAF or web server rules, and disable the plugin if it is not operationally required. Limit retention and exposure of email logs, especially password reset messages, and rotate any credentials or tokens that may have been exposed through logged mail content. Monitor for unexpected API key changes, anomalous REST requests, and suspicious password reset activity.

Remediation

Patch, then assume compromise.

Update the POST SMTP Mailer plugin to a version newer than 2.8.7 that addresses CVE-2023-6875. If a fixed version is not immediately available in the environment, remove or disable the vulnerable plugin until it can be upgraded. After remediation, rotate the plugin API key and review mail logs and WordPress accounts for signs of unauthorized access or password resets that may have occurred prior to patching.
PUBLIC EXPLOITS

Exploits

2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 2 / 2 TOTALView more in app
CVE-2023-6875MaturityPoCVerified exploit

This repository contains a Python proof-of-concept exploit for CVE-2023-6875, targeting the PostSMTP Mailer WordPress plugin (versions <2.8.8). The exploit automates an unauthorized account takeover by abusing the plugin's API endpoints to obtain a password reset token, intercept the reset key from plugin logs, and reset the password for a specified user. The repository consists of a README.md describing the exploit and a single Python script (exploit.py) implementing the attack. The script requires the target URL, username, and new password as arguments, and performs version checking, token acquisition, password reset request, log retrieval, and password change. The attack vector is network-based, exploiting exposed HTTP endpoints on the target WordPress site. The exploit is operational and demonstrates a full account takeover workflow.

gbrshDisclosed Jan 27, 2024pythonnetwork
CVE-2023-6875MaturityPoCVerified exploit

This repository contains a Go-based exploit targeting WordPress installations with the Post SMTP plugin (or similar REST API endpoints). The exploit automates a multi-step attack: 1. It probes for accessible Post SMTP API endpoints to place a token and interact with the mail system. 2. It attempts to enumerate the admin username via the REST API, defaulting to 'admin' if not found. 3. It triggers a password reset for the admin account, then retrieves the reset link from the mail logs exposed by the plugin's API. 4. Using the reset link, it sets a new admin password and logs in as the admin user. 5. Finally, it uploads a ZIP file containing a PHP web shell as a WordPress plugin and provides the attacker with a URL to access the shell. The exploit is operational and provides remote code execution via the uploaded shell. The main code is in 'exploit.go', and the repository also includes a README.md with usage instructions. The attack vector is network-based, requiring access to the target's web interface and specific API endpoints. Several fingerprintable endpoints are hardcoded or constructed based on the target domain, including REST API endpoints and the final shell URL.

hatlesswizardDisclosed Feb 5, 2024gonetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
WpexpertsPost Smtpapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.