CVE-2025-22800

Post SMTP <= 2.9.11 - Missing Authorization via regenerate_qrcode()

2025-01-07 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 2.9.12
Affected Plugin
Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App
Affected Version
<= 2.9.11
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-22800
View all Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App vulnerabilities

At a glance

CVE-2025-22800 is a medium-severity Missing Authorization vulnerability in the Post SMTP WordPress plugin, affecting versions <= 2.9.11. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.9.12; sites on affected versions should update now. Disclosed January 2025, reported by Rafie Muhammad.

Vulnerability Overview

The Post SMTP plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the regenerate_qrcode() function in versions up to, and including, 2.9.11. This makes it possible for authenticated attackers, with subscriber-level access and above, to generate QR codes.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Post SMTP <= 2.9.11 carries this weakness at regenerate_qrcode(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Post SMTP the fix is 2.9.12: builds <= 2.9.11 are affected, anything from 2.9.12 onward is not.

Remediation

Update to version 2.9.12, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Post SMTP 2.9.12 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-22800https://www.wordfence.com/threat-intel/vulnerabilities/id/763a7dec-72e3-46d2-a82e-268c577e0289https://nvd.nist.gov/vuln/detail/CVE-2025-22800

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C