dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-7826

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
The Testimonial plugin for WordPress is vulnerable to SQL Injection via the 'iNICtestimonial' shortcode in all versions up to, and including, 2.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Testimonial WordPress plugin (versions up to 2.3) contains a SQL injection vulnerability in the 'iNICtestimonial' shortcode handler. User-supplied parameters are insufficiently escaped and the existing SQL query lacks prepared statement preparation, allowing authenticated attackers with Contributor-level access to inject arbitrary SQL commands and extract sensitive database contents.

MitigationUpdate the Testimonial plugin to the latest version once available; until then, disable the plugin or implement WAF rules to block SQL injection payloads in shortcode parameters. Review user access controls to limit exposure.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Identify Testimonial plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Testimonial' plugin. Note the version number displayed alongside the plugin name.
    Affected if The plugin is installed and the version is 2.3 or lower (any version up to and including 2.3).
  2. Confirm vulnerable shortcode is available
    Search WordPress database or content files for the string 'iNICtestimonial' in wp_posts table or in theme/template files where shortcodes may be registered.
    Affected if The shortcode handler 'iNICtestimonial' exists in the plugin code, indicating the vulnerable code path is present.
  3. Check for shortcode usage in content
    Query the WordPress database: SELECT * FROM wp_posts WHERE post_content LIKE '%[iNICtestimonial%'; or use WordPress admin search to find posts/pages containing this shortcode.
    Affected if The shortcode is actively used in any published post, page, or custom post type content.
  4. Review user role assignments
    In WordPress admin, go to Users and examine which users have Contributor role or higher. SQL injection via this vulnerability requires an authenticated user with at least Contributor-level access.
    Affected if There are one or more users assigned the Contributor role (or higher) who could potentially exploit this vulnerability.

You are affected if the Testimonial plugin is installed at version 2.3 or lower AND the iNICtestimonial shortcode is present in your environment AND at least one Contributor-level user account exists.

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 the Testimonial plugin to the latest version once available; until then, disable the plugin or implement WAF rules to block SQL injection payloads in shortcode parameters. Review user access controls to limit exposure.

Recommended fix Moderate confidence

Latest version newer than 2.3 from wordpress.org plugin repository

  1. Check the WordPress plugin repository for the Testimonial plugin (iNICtestimonial) to identify if a version newer than 2.3 is available
  2. If a newer version is available, review the plugin changelog or release notes to confirm the SQL injection vulnerability is patched
  3. Update the plugin to the latest available version through the WordPress admin dashboard (Plugins > Add New > Upload or directly via the plugin repository)
  4. After updating, verify the fix by checking that the iNICtestimonial shortcode functions correctly and no longer accepts unsanitized input
  5. Consider using a web application firewall (WAF) as an additional layer of protection until the plugin is updated

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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