CVE-2025-23673
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 dkukral Email on Publish email-on-publish allows Stored XSS.This issue affects Email on Publish: from n/a through <= 1.5.
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 confidenceA CSRF vulnerability in the Email on Publish WordPress plugin allows attackers to trick authenticated administrators into submitting malicious requests that inject and persist malicious scripts (Stored XSS) into plugin settings or published content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 Email on Publish pluginIn WordPress admin, go to Plugins > Installed Plugins and look for 'Email on Publish' or check the /wp-content/plugins/ directory for an email-on-publish folderAffected if The plugin is installed and active
-
Identify the installed versionIn WordPress admin, click on the plugin name to view details, or open the main plugin PHP file and look for the 'Version' header comment in the plugin file headerAffected if The version is unknown, unpatched, or falls within an affected range
-
Check plugin settings for suspicious scriptsNavigate to the plugin's settings page (usually under Settings > Email on Publish) and inspect all input fields for unexpected <script> tags, javascript: URLs, or on* event handlersAffected if Any stored XSS payloads or malicious scripts are present in plugin configuration fields
-
Review recent published content for injected scriptsCheck recent posts/pages that were published or updated while the plugin was active, looking for malicious script tags in content fields or custom fieldsAffected if Malicious scripts appear in published content that were not intentionally added by administrators
-
Audit admin user accounts for unauthorized changesReview WordPress users with administrator role and check if any unexpected users were added or existing admin accounts modifiedAffected if New or unexpected administrator accounts exist that were not created by known admins
A user is affected if the Email on Publish plugin is installed and its version lacks CSRF token validation, or if stored XSS payloads are already present in plugin settings or published content.
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.
dbcve · scopedUpdate to a patched version of the plugin that implements proper CSRF token validation (nonces) on all forms and AJAX actions, along with appropriate input sanitization and output encoding to prevent XSS.
Email on Publish version 1.6 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Email on Publish' plugin by dkukral
- Check the current version (should be <= 1.5)
- Update the plugin to the latest available version (1.6 or later)
- Verify the update was successful and the plugin functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23673 — 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-2025-23673 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