CVE-2025-23627
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 frenchsquared Comment-Emailer comment-emailer allows Stored XSS.This issue affects Comment-Emailer: from n/a through <= 1.0.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 Comment-Emailer WordPress plugin (versions <= 1.0.5) allows authenticated administrators to be tricked into submitting malicious requests that inject persistent cross-site scripting (XSS) payloads into plugin settings or comment email configurations.
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.
-
Confirm WordPress installationVerify the site runs WordPress by checking for wp-config.php in the web root or accessing the WordPress admin dashboard at /wp-admin/Affected if The target is not a WordPress site (this CVE does not apply)
-
Check if Comment-Emailer plugin is installedNavigate to WordPress Admin > Plugins > Installed Plugins and look for 'Comment-Emailer' in the list, or inspect the /wp-content/plugins/ directory for a folder named 'comment-emailer'Affected if The Comment-Emailer plugin is not installed (this CVE does not apply)
-
Identify installed Comment-Emailer versionIn WordPress Admin > Plugins, find Comment-Emailer and view the version number displayed beneath the plugin name; alternatively, open /wp-content/plugins/comment-emailer/comment-emailer.php and check the 'Version' header in the plugin comment blockAffected if The installed version is 1.0.5 or lower (vulnerable)
-
Verify plugin is activeIn WordPress Admin > Plugins, confirm the Comment-Emailer plugin shows as 'Active' rather than 'Inactive'Affected if The plugin is active (the CSRF-to-XSS attack surface is present)
-
Inspect plugin settings for input handlingNavigate to the Comment-Emailer settings page (usually under Settings or Comments menu) and examine how email templates and notification settings are configured; check if the plugin stores user-supplied values without proper sanitization by viewing the plugin settings database table or reviewing the plugin PHP code for missing sanitization functionsAffected if Plugin settings accept user input and store it without sanitization (the XSS injection condition is present)
A user is affected if they have Comment-Emailer plugin version 1.0.5 or lower actively installed on their WordPress site, as this version contains the CSRF-to-persistent-XSS vulnerability in plugin settings.
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 dataUpdate Comment-Emailer to the latest available version; if no update exists, implement anti-CSRF tokens on all plugin forms and ensure all user inputs are properly sanitized before storage and output encoding.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23627 — 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-23627 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