Smtp MailWordPress extension · Photoboxone
CVE-2024-25914
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Photoboxone SMTP Mail.This issue affects SMTP Mail: from n/a through 1.3.20.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Photoboxone SMTP Mail WordPress plugin allows attackers to induce authenticated administrators to perform unintended actions. The flaw lacks anti-CSRF tokens on state-changing operations, enabling malicious requests to be forged from other sites.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Smtp MailWordPress extension
<= 1.3.20CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Photoboxone SMTP Mail plugin installationAccess your WordPress site via FTP or file manager, navigate to wp-content/plugins/ and check if a folder named 'photoboxone-smtp-mail' or similar exists. Alternatively, log into WordPress admin and go to Plugins > Installed Plugins to find it in the list.Affected if The plugin folder is not present in the plugins directory
-
Identify the installed plugin versionIf the plugin is installed, open the main plugin PHP file (typically named something like photoboxone-smtp-mail.php) and look for the version comment header at the top of the file. In WordPress admin, the version is displayed next to the plugin name in the Plugins list.Affected if The displayed version number is 1.3.20 or lower
-
Verify the vulnerability condition existsExamine the plugin PHP files that handle form submissions and AJAX actions (typically in the main plugin file or files handling settings and mail operations). Look for wp_nonce_field(), wp_verify_nonce(), or check_admin_referer() calls on state-changing operations like saving settings or triggering mail actions.Affected if State-changing functions lack nonce verification calls, meaning no anti-CSRF tokens are present in forms or AJAX handlers
You are affected if the Photoboxone SMTP Mail plugin is installed at version 1.3.20 or lower and the plugin code handling settings or mail operations does not implement nonce validation on forms that modify plugin state.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement nonces (anti-CSRF tokens) on all forms and AJAX actions that modify plugin settings or trigger mail operations; add SameSite attributes to cookies and validate Origin/Referer headers.
Fix this in Smtp Mail
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-25914 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data