CVE-2025-23677
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 DSmidge HTTP to HTTPS link changer by Eyga.net https-links-in-content allows Stored XSS.This issue affects HTTP to HTTPS link changer by Eyga.net: from n/a through <= 0.2.4.
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 · high confidenceA CSRF vulnerability in the DSmidge HTTP to HTTPS link changer WordPress plugin (versions <= 0.2.4) allows authenticated administrators to be tricked into performing unintended actions that inject malicious scripts. Since the resulting XSS is stored in the database, it persists and executes whenever users view affected 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.
-
Confirm DSmidge plugin is installedNavigate to WordPress admin dashboard under Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'dsmidge-http-to-https-link-changer' or similarAffected if The plugin folder exists in the WordPress plugins directory
-
Identify installed plugin versionIn the WordPress admin, find the DSmidge plugin in the Plugins list and read the version number displayed beneath the plugin name; alternatively, check the main plugin PHP file for a 'Version' header commentAffected if The installed version is 0.2.4 or lower
-
Verify plugin is activeIn WordPress admin, check that the DSmidge plugin shows as 'Active' in the Plugins listAffected if The plugin is active and the version is 0.2.4 or lower (inactive plugins with a vulnerable version are not exploitable)
-
Inspect database for stored scriptsSearch WordPress database tables (particularly wp_posts, wp_options, or any custom tables the plugin may use) for suspicious script tags, javascript: URIs, or event handlers in fields that could be modified by the plugin's link conversion featureAffected if Database contains unexpected script tags or javascript: links that were not intentionally added by an administrator
You are affected if the DSmidge plugin is installed, active, and running version 0.2.4 or lower, and malicious scripts are present in the database as a result of the CSRF vulnerability.
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 nonce-based CSRF protection on all admin actions and add proper input sanitization with output escaping to prevent stored XSS. Users should update to a patched version when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23677 — 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-23677 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