# CVE-2023-6629: POST SMTP Mailer <= 2.8.6 - Reflected Cross-Site Scripting via msg

> Unauthenticated attackers can inject arbitrary web scripts via the msg parameter, requiring user interaction to execute.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jan 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9cxx-v6f7-6hpm

## What is CVE-2023-6629?

CVE-2023-6629 is a medium-severity cross-site scripting vulnerability in saadiqbal Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App, published on 3 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘msg’ parameter in all versions up to, and including, 2.8.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE-2023-6621 appears to be a duplicate of this issue. CVE-2024-29128 appears to be a duplicate of this issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-6629?

It affects 1 product.


Products: Wpexperts Post Smtp.

## How do I fix CVE-2023-6629?

No fix has been published for CVE-2023-6629 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-6629 being exploited?

There is no known exploitation of CVE-2023-6629 in the wild and no public exploit code.

## Other vulnerabilities in saadiqbal Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App

- [CVE-2023-6875](https://insights.sbomify.com/CVE-2023-6875/): Auth bypass in Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App (critical 9.8)
- [CVE-2023-3179](https://insights.sbomify.com/CVE-2023-3179/): POST SMTP Mailer < 2.5.7 - Account Takeover via CSRF (high 8.8)
- [CVE-2023-52233](https://insights.sbomify.com/CVE-2023-52233/): WordPress POST SMTP Mailer plugin <= 2.8.6 - Broken Access Control on API vulnerability (high 8.6)
- [CVE-2024-52436](https://insights.sbomify.com/CVE-2024-52436/): WordPress Post SMTP plugin <= 2.9.9 - SQL Injection vulnerability (high 7.6)
- [CVE-2025-0521](https://insights.sbomify.com/CVE-2025-0521/): Post SMTP <= 3.0.2 - Unauthenticated Stored Cross-Site Scripting (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6629 and fix it if it is affected.

What it is: CVE-2023-6629 is a medium-severity cross-site scripting vulnerability in saadiqbal Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App, published on 3 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-6629 in the wild and no public exploit code.

Affected product: saadiqbal Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-6629/ (Markdown: https://insights.sbomify.com/CVE-2023-6629/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6629
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6629
- OSV: https://osv.dev/vulnerability/CVE-2023-6629

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-6629/
Summaries are generated and may contain mistakes; the official description above is the record.