Wp Testimonial WidgetWordPress extension · Starkdigital
CVE-2024-43966
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Stark Digital WP Testimonial Widget.This issue affects WP Testimonial Widget: from n/a through 3.1.
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 confidenceSQL injection vulnerability in Stark Digital WP Testimonial Widget plugin allows authenticated attackers to inject malicious SQL queries through unsanitized input parameters in the plugin's database queries.
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 Testimonial WidgetWordPress extension
<= 3.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Testimonial Widget' or 'Starkdigital WP Testimonial Widget'. Check the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file header for the Version comment.Affected if The plugin is installed and the version is 3.1 or lower.
-
Confirm plugin is activeIn WordPress admin > Plugins, verify the plugin status shows as 'Active'. Also check any pages/widgets where the testimonial widget has been added via Appearance > Widgets or the block editor.Affected if The plugin is active and being used on the site.
-
Check for existing WordPress user accountsNavigate to Users > All Users in the WordPress admin panel. Review the list of registered users. Any account with Subscriber, Contributor, Author, Editor, or Administrator role could potentially exploit this authenticated SQL injection.Affected if There are user accounts on the WordPress site (even Subscriber-level is sufficient for exploitation).
-
Identify exposed testimonial endpointsCheck the plugin settings under WP Testimonial Widget in the admin menu. Look for any frontend display shortcodes or widgets that render testimonial queries. Common endpoints include pages with [testimonial_widget] shortcode or testimonial archive pages.Affected if Testimonial functionality is publicly accessible and queries the database.
A user is affected if the Starkdigital WP Testimonial Widget plugin version 3.1 or lower is installed and active on the WordPress site with at least one user account that can authenticate.
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 dataUpdate to the latest version of WP Testimonial Widget which should contain proper input sanitization using prepared statements, or implement parameterized queries in the affected code paths.
Fix this in Wp Testimonial Widget
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-43966 — 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-2024-43966 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