WdsocialwidgetsWordPress extension · Web Dorado
CVE-2023-46619
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 WebDorado WDSocialWidgets plugin <= 1.0.15 versions.
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 WebDorado WDSocialWidgets plugin versions 1.0.15 and below allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests.
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
WdsocialwidgetsWordPress extension
<= 1.0.15CVSS 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.
-
Locate the WDSocialWidgets plugin installationCheck your WordPress site's wp-content/plugins/ directory for a folder named 'wd-social-widget' or 'wdsocialwidgets'. The main plugin file typically contains version information in its header comment.Affected if The plugin folder exists on the server.
-
Determine the installed plugin versionOpen the main plugin PHP file (usually wd-social-widget.php or similar) and look for the 'Version' field in the plugin header comment at the top of the file. Alternatively, check the plugin's readme.txt file for the 'Stable tag' or version number.Affected if The version number displayed is 1.0.15 or lower.
-
Verify state-changing operations lack nonce protectionInspect the main plugin PHP files for form submissions and AJAX action handlers (look for 'add_action' calls with 'wp_ajax_' or 'wp_ajax_nopriv_' hooks). Check if these handlers validate nonces using functions like 'wp_verify_nonce' or 'check_admin_referer' before processing requests.Affected if Form handling code or AJAX action callbacks do not validate nonces before processing state-changing requests.
-
Review admin settings pages for CSRF-protected formsNavigate to the plugin's admin settings pages in WordPress admin panel. Look for forms that submit to admin-post.php or ajax endpoints. Use browser developer tools to inspect form HTML for hidden nonce fields (typically named '_wpnonce' or '_wp_http_referer').Affected if Forms on plugin settings pages are missing nonce token fields.
You are affected if the WDSocialWidgets plugin version is 1.0.15 or lower AND the plugin contains form submissions or AJAX actions that do not validate CSRF tokens.
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 anti-CSRF tokens (nonce validation) on all state-changing operations (form submissions and AJAX actions) within the plugin; update to a patched version if available.
Fix this in Wdsocialwidgets
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-46619 — 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-46619 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