dbcve.org
Hms TestimonialsWordPress extension · Hitmyserver

CVE-2013-4240

MEDIUM · 6.8 CVSS v2.0 Published 2014-04-02
Fix available
A fix is available. Upgrade to after 2.0.10 or later.
See remediation →
77/100
Remediation priority · High
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
Multiple cross-site request forgery (CSRF) vulnerabilities in the HMS Testimonials plugin before 2.0.11 for WordPress allow remote attackers to hijack the authentication of administrators for requests that (1) add new testimonials via the hms-testimonials-addnew page, (2) add new groups via the hms-testimonials-addnewgroup page, (3) change default settings via the hms-testimonials-settings page, (4) change advanced settings via the hms-testimonials-settings-advanced page, (5) change custom fields settings via the hms-testimonials-settings-fields page, or (6) change template settings via the hms-testimonials-templates-new page to wp-admin/admin.php.

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 HMS Testimonials WordPress plugin before version 2.0.11 lacks anti-CSRF tokens (nonces) in multiple admin forms accessed via wp-admin/admin.php. This allows remote attackers to trick authenticated administrators into unknowingly submitting requests to add/modify testimonials, groups, settings, and templates by embedding malicious links or forms on external sites.

MitigationUpgrade HMS Testimonials plugin to version 2.0.11 or later which implements anti-CSRF nonce validation in all admin forms.

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
Hms TestimonialsWordPress extension
Affected:<= 2.0.10= 1.1= 1.2= 1.3= 1.4= 1.4.1= 1.5= 1.6= 1.6.1= 1.6.2= 1.7= 1.7.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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 HMS Testimonials plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'HMS Testimonials' or 'Hms Testimonials' in the list of active or installed plugins.
    Affected if The plugin is present in the WordPress installation, regardless of activation status.
  2. Determine installed plugin version
    In the Plugins list, locate the HMS Testimonials entry. The version number is displayed below the plugin name. Alternatively, inspect the plugin header in wp-content/plugins/hms-testimonials/hms-testimonials.php or similar main plugin file.
    Affected if The installed version is 2.0.10 or lower, or specifically 1.1, 1.2, 1.3, 1.4, 1.4.1, 1.5, 1.6, 1.6.1, 1.6.2, 1.7, or 1.7.1.
  3. Confirm admin access to vulnerable forms
    Navigate to the plugin admin section via wp-admin/admin.php?page=hms-testimonials or similar HMS Testimonials admin menu item. Verify you can access testimonial, group, settings, or template management forms.
    Affected if The WordPress site has an authenticated administrator who can access the plugin admin forms.
  4. Inspect admin forms for nonce validation
    Examine the plugin PHP files that handle admin form submissions (typically in the plugin directory under includes/admin/ or directly in the main plugin file). Look for wp_nonce_field() or wp_nonce_url() calls in forms that submit to wp-admin/admin.php.
    Affected if The admin form handlers lack nonce verification code, meaning forms do not include or validate anti-CSRF tokens.

A user is affected if the HMS Testimonials plugin is installed with version 2.0.10 or lower, an authenticated administrator can access the plugin admin forms, and those forms lack nonce validation in the code.

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.

From vendor data
Upgrade available Upgrade to a release after 2.0.10
Interim mitigation

Upgrade HMS Testimonials plugin to version 2.0.11 or later which implements anti-CSRF nonce validation in all admin forms.

Fix this in Hms Testimonials Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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