dbcve.org
Strong TestimonialsWordPress extension · Wpchill

CVE-2024-47362

HIGH · 8.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 3.1.17 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Missing Authorization vulnerability in WP Chill Strong Testimonials strong-testimonials.This issue affects Strong Testimonials: from n/a through <= 3.1.16.

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 confidence

A missing authorization vulnerability exists in the Strong Testimonials WordPress plugin (versions <= 3.1.16) that allows unauthenticated or low-privilege users to access functionality they should not be able to reach. This broken access control issue has a CVSS base score of 8.8, indicating the vulnerability is remotely exploitable and can lead to unauthorized data access or modification.

MitigationUpdate Strong Testimonials plugin to the latest version (3.1.17 or later) which should contain proper authorization checks. If immediate update is not possible, restrict access to vulnerable endpoints at the server level as a temporary measure.

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
Strong TestimonialsWordPress extension
Affected:< 3.1.17

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Locate the Strong Testimonials plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Strong Testimonials' by Wpchill. The version number is displayed below the plugin name. Alternatively, inspect the plugin's main PHP file header for the 'Version' tag.
    Affected if The displayed version is 3.1.16 or lower
  2. Verify the exact version number
    Compare the installed version against the affected range. Version 3.1.16 and all prior versions (e.g., 3.1.15, 3.1.14, etc.) are vulnerable. Only version 3.1.17 and later are patched.
    Affected if The installed version is <= 3.1.16
  3. Confirm WordPress user roles present
    Review the list of registered WordPress users and their assigned roles via Users > All Users in the admin dashboard. Note any users with low-privilege roles (subscriber, contributor, author) who should not have access to plugin settings.
    Affected if Users with limited roles exist alongside the vulnerable plugin version, indicating potential for unauthorized access
  4. Check plugin capability configuration
    Inspect the Strong Testimonials plugin settings page (Strong Testimonials > Settings) to determine if any settings or submission forms are accessible to non-administrator roles.
    Affected if Non-administrator roles have permission to submit or view testimonials when the plugin version is <= 3.1.16

If the Strong Testimonials plugin version is 3.1.16 or lower, the site is affected by this missing authorization vulnerability and unauthorized users may access restricted functionality.

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 3.1.17 or later
Fixed in 3.1.17
Interim mitigation

Update Strong Testimonials plugin to the latest version (3.1.17 or later) which should contain proper authorization checks. If immediate update is not possible, restrict access to vulnerable endpoints at the server level as a temporary measure.

Recommended fix High confidence

Strong Testimonials version 3.1.17

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Dashboard > Plugins in your WordPress admin panel
  3. 3. Find 'Strong Testimonials' in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to version 3.1.17 or later
  5. 5. Verify the plugin version after update by checking the installed version number
  6. 6. Test the testimonial submission functionality to ensure the plugin is working correctly

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

Fix this in Strong Testimonials Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47362 — 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-47362 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