dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-38345

HIGH · 8.1 CVSS v3.1 Published 2024-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
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
A cross-site request forgery vulnerability exists in Sola Testimonials versions prior to 3.0.0. If this vulnerability is exploited, an attacker allows a user who logs in to the WordPress site where the affected plugin is enabled to access a malicious page. As a result, the user may perform unintended operations on the WordPress site.

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

A cross-site request forgery (CSRF) vulnerability exists in the Sola Testimonials WordPress plugin versions prior to 3.0.0. The plugin fails to properly validate CSRF tokens on state-changing requests, allowing authenticated users to be tricked into performing unintended administrative actions via maliciously crafted web pages.

MitigationUpdate Sola Testimonials to version 3.0.0 or later to obtain the security patch. If immediate update is not possible, disable the plugin until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Verify Sola Testimonials plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Sola Testimonials' in the list, or inspect the file /wp-content/plugins/sola-testimonials/ for existence
    Affected if The plugin is installed and present in the WordPress plugins directory
  2. Check the installed version number
    In WordPress admin, go to Plugins > Installed Plugins, find Sola Testimonials, and note the version number displayed below the plugin name
    Affected if Version is lower than 3.0.0 (e.g., 2.x.x, 1.x.x, or any version prior to 3.0.0)
  3. Confirm plugin is active
    In Plugins > Installed Plugins, verify the plugin status shows 'Active' under Sola Testimonials
    Affected if Plugin status is Active (inactive plugins cannot be exploited)
  4. Identify state-changing features in use
    Review plugin settings for any enabled features that perform administrative actions such as creating, editing, or deleting testimonials, managing settings, or importing/exporting data
    Affected if Any administrative or state-changing plugin features are enabled and accessible to authenticated users

Your environment is affected if Sola Testimonials plugin is installed, active, and running a version lower than 3.0.0 with administrative features enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Sola Testimonials to version 3.0.0 or later to obtain the security patch. If immediate update is not possible, disable the plugin until the patch can be applied.

Recommended fix High confidence

Sola Testimonials version 3.0.0 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Sola Testimonials plugin
  4. Check the current installed version - if it is below 3.0.0, an update is needed
  5. Update the plugin to version 3.0.0 or later through the WordPress plugin update mechanism
  6. Verify the plugin was updated successfully and functions normally

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

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