Easy Call Now By ThikshareWordPress extension · Dangngocbinh

CVE-2023-47819

HIGH · 8.8 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to after 1.1.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Dang Ngoc Binh Easy Call Now by ThikShare plugin <= 1.1.0 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 · low confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Easy Call Now WordPress plugin by ThikShare versions 1.1.0 and below allows attackers to induce authenticated users to perform unintended administrative actions via maliciously crafted requests.

MitigationImplement WordPress nonces (wp_nonce_field) in all forms and action links, and verify nonce validation using check_admin_referer() or wp_verify_nonce() before processing any state-changing operations.

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
Easy Call Now By ThikshareWordPress extension
Affected:<= 1.1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Easy Call Now plugin is installed
    Go to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Easy Call Now' or 'Dangngocbinh Easy Call Now By Thikshare' in the list of active plugins
    Affected if the plugin appears in the installed plugins list
  2. Determine installed plugin version
    In the Plugins page, click on the plugin name or view details to read the version number displayed (e.g., 'Version 1.1.0' or lower)
    Affected if the version displayed is 1.1.0 or any version lower than 1.1.0
  3. Inspect plugin for missing nonce validation
    Access the plugin files via FTP or file manager, locate the main plugin PHP file (usually in wp-content/plugins/easy-call-now or similar), and search for forms or action handlers - check if wp_nonce_field, check_admin_referer, or wp_verify_nonce are used before processing form submissions or admin actions
    Affected if forms or action links exist in the plugin without nonce protection (no wp_nonce_field in forms and no nonce verification before processing)
  4. Check if plugin exposes admin actions
    Review the plugin code for any admin action hooks (admin_post_, wp_ajax_, or similar) that handle state-changing operations and verify if these endpoints validate nonces before executing changes
    Affected if admin action handlers process requests without verifying nonce tokens

A user is affected if the Easy Call Now plugin by ThikShare version 1.1.0 or below is installed AND the plugin lacks nonce validation on its forms or administrative action handlers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.1.0
Interim mitigation

Implement WordPress nonces (wp_nonce_field) in all forms and action links, and verify nonce validation using check_admin_referer() or wp_verify_nonce() before processing any state-changing operations.

Recommended fix Moderate confidence

1.1.1 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Easy Call Now By Thikshare' plugin
  4. 4. Check if an update is available and update to the latest version
  5. 5. Verify the plugin updated successfully

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Easy Call Now By Thikshare Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47819 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47819 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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