dbcve.org
Visitors OnlineWordPress extension · Bestwebsoft

CVE-2015-9325

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-16
Fix available
A fix is available. Upgrade to 0.4 or later.
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
The visitors-online plugin before 0.4 for WordPress has SQL injection.

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 the visitors-online WordPress plugin versions prior to 0.4 allows attackers to inject malicious SQL queries through unsanitized input, potentially enabling unauthorized database access, data exfiltration, or complete site compromise.

MitigationUpdate the visitors-online plugin to version 0.4 or later immediately. If no update is available, deactivate and remove the plugin until a patched version is released.

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
Visitors OnlineWordPress extension
Affected:< 0.4

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 visitors-online plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Visitors Online' or 'Bestwebsoft Visitors Online' plugin, or inspect the wp-content/plugins/ directory for a folder named 'visitors-online' or similar.
    Affected if The plugin is found installed and active on the WordPress site.
  2. Determine the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find the Visitors Online plugin and read the version number from the plugin description. Alternatively, open the main plugin PHP file (usually visitors-online.php or bws-visitors-online.php) in wp-content/plugins/ and look for the 'Version' header comment.
    Affected if The version displayed is lower than 0.4 (e.g., 0.3, 0.2, or no version shown).
  3. Verify the plugin is active
    In WordPress admin > Plugins, confirm whether the Visitors Online plugin has an 'Active' status under the plugin name.
    Affected if The plugin is active and running on the site.
  4. Check for unsanitized user input usage
    Inspect the plugin PHP files in wp-content/plugins/visitors-online/ for direct use of $_GET, $_POST, or $_REQUEST variables in SQL queries without proper escaping or prepared statements. Search for patterns like '$_GET' or '$_POST' appearing near SQL queries.
    Affected if The code contains direct use of unsanitized input in SQL queries.

If the Visitors Online plugin is installed with a version lower than 0.4 and is active, the site is affected by this SQL injection vulnerability.

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
Upgrade available Upgrade to 0.4 or later
Fixed in 0.4
Interim mitigation

Update the visitors-online plugin to version 0.4 or later immediately. If no update is available, deactivate and remove the plugin until a patched version is released.

Recommended fix High confidence

version 0.4

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Visitors Online' plugin
  4. Check if the current version is below 0.4
  5. If vulnerable, click 'Update Now' to upgrade to version 0.4
  6. Alternatively, navigate to Plugins > Add New > Upload to manually upload the latest version of the visitors-online plugin
  7. After update, verify the plugin version is 0.4 or higher

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

Fix this in Visitors Online Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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