dbcve.org
Wp Testimonial WidgetWordPress extension · Starkdigital

CVE-2024-7390

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-21
Fix available
A fix is available. Upgrade to after 3.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
The WP Testimonial Widget plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the fnSaveTestimonailOrder function in all versions up to, and including, 3.1. This makes it possible for unauthenticated attackers to change the order of testimonials.

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 confidence

The WP Testimonial Widget plugin for WordPress has a broken access control vulnerability in the fnSaveTestimonailOrder function. This function, which handles reordering testimonials, lacks a capability check (e.g., current_user_can), allowing any unauthenticated user to modify testimonial order via a direct AJAX call.

MitigationUpdate the plugin to version 3.2 or later which includes proper capability verification. Until an update is available, consider disabling the plugin or implementing a web application firewall (WAF) rule to block unauthorized access to the vulnerable endpoint.

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
Affected:<= 3.1

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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. Confirm plugin is installed
    Log in to WordPress admin, navigate to Plugins > Installed Plugins, and look for 'Starkdigital Wp Testimonial Widget' or 'WP Testimonial Widget' in the list
    Affected if The plugin appears in the installed plugins list regardless of activation status
  2. Check installed version
    In the plugins list, locate the plugin and view the version number under the plugin name. Alternatively, check the plugin header in the main PHP file (typically in wp-content/plugins/wp-testimonial-widget/ or similar path)
    Affected if The version number is 3.1 or lower
  3. Verify AJAX endpoint exposure
    Check if the WordPress AJAX handler (wp-admin/admin-ajax.php) responds to the testimonial order action. Inspect the plugin code for the function 'fnSaveTestimonailOrder' (note the typo in Testimonail) and verify if it is hooked to wp_ajax_ without a preceding current_user_can check
    Affected if The AJAX action is registered and accessible without authentication, and the function lacks a capability check like current_user_can('manage_options') or similar
  4. Test unauthenticated access (optional)
    If you have a staging environment, attempt a POST request to your site's wp-admin/admin-ajax.php with the action parameter set to the testimonial order save action (e.g., action=save_testimonial_order) without providing authentication cookies
    Affected if The request succeeds and modifies testimonial order without authentication

You are affected if the plugin is installed with version 3.1 or lower and the AJAX endpoint for saving testimonial order is accessible without any capability verification.

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 3.1
Interim mitigation

Update the plugin to version 3.2 or later which includes proper capability verification. Until an update is available, consider disabling the plugin or implementing a web application firewall (WAF) rule to block unauthorized access to the vulnerable endpoint.

Recommended fix Moderate confidence

Version 3.2 or later (verify latest version on wordpress.org/plugins/wp-testimonial-widget/)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the WP Testimonial Widget plugin
  4. 4. Check if an update is available and update to version 3.2 or higher
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload/install it

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

Fix this in Wp Testimonial Widget Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-7390 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