CVE-2024-12323VulnerabilityPublished 10 Dec 2024

CVE-2024-12323: turboSMTP (WordPress plugin) · Cross-site Scripting

Affects turboSMTP (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
dueclic turboSMTP	Affected *	Fixed in–

AI-suggested

Organizations should immediately verify if they use the turboSMTP WordPress plugin and determine the version in use. Since no official patches are currently available, administrators should implement the following mitigations: 1) Apply strict input validation and output encoding on the 'page' parameter at the web application firewall (WAF) or reverse proxy level to block malicious payloads. 2) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 3) Educate users, especially those with login access, to avoid clicking suspicious or unsolicited links. 4) Monitor web server and application logs for unusual requests targeting the 'page' parameter. 5) Limit user privileges within WordPress to reduce the impact of potential session hijacking. 6) Regularly back up WordPress sites and maintain an incident response plan for web application attacks. 7) Stay alert for official patches or updates from dueclic and apply them promptly once released. 8) Consider temporarily disabling or replacing the turboSMTP plugin if feasible until a fix is available.

Description

The turboSMTP plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘page’ parameter in all versions up to, and including, 4.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 while logged in to turboSMTP.

Impact

The primary impact of CVE-2024-12323 is on the confidentiality and integrity of users interacting with vulnerable turboSMTP WordPress sites. Successful exploitation can lead to theft of authentication tokens, session hijacking, unauthorized actions performed on behalf of users, and potential exposure of sensitive information. While availability is not directly affected, the compromise of user accounts or data can have downstream operational and reputational consequences. Organizations relying on turboSMTP for email services within WordPress environments face increased risk of targeted phishing or social engineering attacks leveraging this vulnerability. The requirement for user interaction limits automated widespread exploitation but does not eliminate risk, especially in environments with high user traffic or where users have elevated privileges. The vulnerability could be leveraged as a foothold for further attacks within an organization's network or to spread malware via injected scripts. Given the plugin's role in email delivery, attackers might also manipulate email content or delivery processes indirectly if combined with other vulnerabilities.

Summary

CVE-2024-12323 is a reflected Cross-Site Scripting (XSS) vulnerability identified in the turboSMTP plugin for WordPress, affecting all versions up to and including 4.6. The vulnerability stems from improper neutralization of input during web page generation, specifically inadequate sanitization and escaping of the 'page' parameter. This flaw allows unauthenticated attackers to craft malicious URLs containing arbitrary JavaScript code that, when clicked by a logged-in user, executes in the context of the victim's browser session. The attack vector is network-based with low attack complexity and no privileges required, but it necessitates user interaction (clicking a malicious link). The vulnerability impacts confidentiality and integrity by potentially exposing sensitive user data or enabling session hijacking, but it does not affect system availability. The scope is limited to users logged into turboSMTP-enabled WordPress sites. Although no exploits are currently known in the wild, the vulnerability is publicly disclosed and assigned a CVSS 3.1 base score of 6.1, indicating a medium severity level. Due to the widespread use of WordPress and the turboSMTP plugin for email delivery, this vulnerability poses a tangible risk to many organizations relying on these technologies. The lack of official patches at the time of disclosure necessitates immediate mitigation efforts to prevent exploitation.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 05:28 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats