CVE-2025-68573
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 Alessandro Piconi Simple Keyword to Link simple-keyword-to-link allows Cross Site Request Forgery.This issue affects Simple Keyword to Link: 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Simple Keyword to Link WordPress plugin allows attackers to induce authenticated administrators to perform unwanted actions. The plugin lacks proper nonce validation on state-changing requests, enabling attackers to craft malicious links or forms that execute actions with the privileges of a logged-in administrator.
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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Verify plugin installationNavigate to WordPress admin dashboard > Plugins and confirm 'Simple Keyword to Link' is installed and activeAffected if plugin is installed and active
-
Check plugin versionIn Plugins list, click on 'Simple Keyword to Link' to view the installed version number, then compare against any known vulnerable versionsAffected if version is within an affected range if documented
-
Inspect plugin source for nonce implementationAccess plugin files via FTP or file manager, locate the main plugin PHP file (typically in wp-content/plugins/simple-keyword-to-link/), and search for 'wp_nonce_field' or 'check_admin_referer' function callsAffected if no nonce validation functions are found in the code
-
Examine forms for nonce fieldsIn plugin settings pages, view the HTML source of any forms to verify the presence of a hidden input containing a nonce field (look for '_wpnonce' or similar)Affected if forms do not contain nonce token fields
-
Check AJAX endpoints for nonce verificationReview plugin PHP files for AJAX handlers (admin-ajax.php calls) and verify they include nonce verification using 'check_ajax_referer' or 'wp_verify_nonce'Affected if AJAX endpoints lack server-side nonce verification
The environment is affected if the Simple Keyword to Link plugin is installed and its state-changing requests (forms or AJAX operations) lack proper nonce validation as verified through code inspection.
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 WordPress nonces (anti-CSRF tokens) on all forms and AJAX endpoints within the plugin, and verify these nonces on server-side processing to validate request authenticity.
- 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-68573 — 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-68573 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