dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-40636

CRITICAL · 9.3 CVSS v4.0 Published 2025-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
SQL injection vulnerability in Joomla module mod_vvisit_counter v2.0.4j3. This vulnerability allows an attacker to retrieve database content via the ‘cip_vvisitcounter’ cookie at all endpoints where the plugin counts visits.

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

SQL injection vulnerability in Joomla module mod_vvisit_counter v2.0.4j3 allows remote attackers to inject malicious SQL commands through the unvalidated 'cip_vvisitcounter' cookie parameter. The cookie value is used directly in SQL queries without proper sanitization or parameterized queries, enabling database content extraction.

MitigationDisable or remove the vulnerable mod_vvisit_counter module immediately. Apply input validation and use parameterized queries for the cookie value, or await an official vendor patch.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Check if mod_vvisit_counter module is installed
    Navigate to Joomla administrator panel, go to Extensions > Modules, and search for 'mod_vvisit_counter' in the list of installed modules
    Affected if The module appears in the installed modules list
  2. Verify the module version
    In Extensions > Modules, click on the mod_vvisit_counter entry and check the version displayed in the module details or manifest file at /modules/mod_vvisit_counter/mod_vvisit_counter.xml
    Affected if Version is 2.0.4j3 or earlier (no fixed version provided, but this is the known vulnerable version)
  3. Confirm the module is enabled
    In Extensions > Modules, check the status column for mod_vvisit_counter - look for a green checkmark or 'Enabled' status
    Affected if The module status shows as Enabled or Published
  4. Inspect cookie parameter usage in the module code
    Examine the module's main PHP file (typically /modules/mod_vvisit_counter/helper.php or similar) for direct use of $_COOKIE['cip_vvisitcounter'] in SQL queries without sanitization
    Affected if Code contains direct SQL queries using the cookie value without prepared statements or escaping functions

A user is affected if mod_vvisit_counter version 2.0.4j3 is installed, enabled, and the module code uses the cip_vvisitcounter cookie value directly in SQL queries without sanitization.

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

Disable or remove the vulnerable mod_vvisit_counter module immediately. Apply input validation and use parameterized queries for the cookie value, or await an official vendor patch.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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