Wp Links PageWordPress extension · Wplinkspage
CVE-2023-47651
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 Robert Macchi WP Links Page.This issue affects WP Links Page: from n/a through 4.9.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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP Links Page WordPress plugin versions through 4.9.4 allows unauthenticated attackers to trick authenticated administrators into performing unintended actions by luring them to visit malicious pages that force their browser to send crafted requests to the vulnerable site.
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
Wp Links PageWordPress extension
<= 4.9.4CVSS 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.
-
Verify WP Links Page plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Links Page' or 'Wplinkspage Wp Links Page' in the list of active pluginsAffected if the plugin appears in the installed plugins list
-
Check installed plugin versionIn the Plugins list, click on the plugin name or view details to find the version number displayedAffected if the version is 4.9.4 or lower (any version through 4.9.4)
-
Inspect plugin forms for nonce fieldsView page source of any admin page created by the plugin (e.g., link management pages). Look for input fields named '_wpnonce' or 'nonce' in forms that perform state-changing actions like adding, editing, or deleting linksAffected if forms lack _wpnonce or nonce input fields, or if the nonce field is present but not validated server-side (requires code review)
-
Inspect AJAX actions for nonce verificationExamine plugin JavaScript files and PHP AJAX handlers. Check if AJAX requests include a nonce parameter and if the PHP handler verifies it using check_ajax_referer or wp_verify_nonceAffected if AJAX actions lack nonce verification or the nonce is not checked server-side before processing requests
A user is affected if the WP Links Page plugin version 4.9.4 or lower is installed and the plugin forms or AJAX actions do not implement WordPress nonce validation for state-changing operations.
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 actions that perform state-changing operations, and validate these nonces server-side before processing requests. Additionally, set SameSite=Strict or SameSite=Lax attributes on session cookies.
Fix this in Wp Links Page
Scoped from the published advisory
- 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-2023-47651 — 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-2023-47651 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