dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-7662

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-15
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 Gestion de tarifs plugin for WordPress is vulnerable to SQL Injection via the 'tarif' and 'intitule' shortcodes in all versions up to, and including, 1.4 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 Gestion de tarifs WordPress plugin versions up to 1.4 contains SQL injection vulnerabilities in the 'tarif' and 'intitule' shortcode handlers due to insufficient user input escaping and lack of prepared SQL statements, allowing authenticated attackers with Contributor-level access or higher to inject malicious SQL queries and extract sensitive database information.

MitigationUpdate to a patched version of the plugin (>1.4) when released, or replace with a secure alternative. Until the patch is available, disable the vulnerable shortcodes or restrict usage to Administrator-level users only.

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. Verify Gestion de tarifs plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'Gestion de tarifs' in the installed plugins list, or inspect the wp-content/plugins directory for a folder named 'gestion-de-tarifs' or similar.
    Affected if The plugin appears in the installed plugins list and is activated.
  2. Check installed plugin version
    In WordPress Admin > Plugins, click on the plugin details to view the version number, or open the main plugin PHP file (usually named index.php or gestion-de-tarifs.php) and read the Version header in the plugin comment block.
    Affected if The reported version is 1.4 or lower.
  3. Confirm shortcode handlers exist
    Inspect the plugin source code for registered shortcode handlers by searching for 'add_shortcode' calls, specifically looking for 'tarif' and 'intitule' shortcode names.
    Affected if The shortcodes 'tarif' and/or 'intitule' are registered in the plugin.
  4. Check for Contributor+ user accounts
    In WordPress Admin > Users, review the list of existing users and their assigned roles. Identify any users with the Contributor, Author, Editor, or Administrator roles.
    Affected if There is at least one user account with Contributor-level access or higher (excluding Administrator only).
  5. Verify shortcode usage in content
    Search WordPress posts, pages, and custom post types for the presence of [tarif] or [intitule] shortcode strings using the WordPress admin or by querying the wp_posts table in the database.
    Affected if The vulnerable shortcodes are present in any published content.

The environment is affected if the Gestion de tarifs plugin version 1.4 or lower is installed and active, the vulnerable shortcodes exist, and there is at least one user with Contributor-level access or higher who could exploit the SQL injection.

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 to a patched version of the plugin (>1.4) when released, or replace with a secure alternative. Until the patch is available, disable the vulnerable shortcodes or restrict usage to Administrator-level users only.

Recommended fix Moderate confidence

Version 1.5 or later of the Gestion de tarifs plugin

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Gestion de tarifs' plugin
  4. Check if an update is available for the plugin
  5. If an update is available, update to the latest version (version 1.5 or later)
  6. Verify the update completed successfully
  7. Ensure any users with Contributor-level or higher access are trusted, as this vulnerability requires authentication to exploit
Caveat No breaking changes expected for this security patch update

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-7662 — 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-7662 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