dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-2107

HIGH · 7.5 CVSS v3.1 Published 2025-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
The ArielBrailovsky-ViralAd plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter of the printResultAndDie() function in all versions up to, and including, 1.0.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This only appears to be exploitable on very old versions of WordPress.

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 ArielBrailovsky-ViralAd WordPress plugin has a SQL injection vulnerability in the printResultAndDie() function where the 'id' parameter is not properly escaped or sanitized before being used in a database query. Unauthenticated attackers can inject malicious SQL queries through this parameter to extract sensitive information from the database. The vulnerability exists due to both insufficient input escaping and lack of prepared statements in the SQL query.

MitigationUpdate the plugin to version 1.0.9 or later once the patch is released. If no update is available, consider removing the plugin or implementing firewall rules at the web application level to block SQL injection attempts on the affected parameter.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the plugin version
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'ViralAd' or 'ArielBrailovsky-ViralAd'. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file (typically in wp-content/plugins/viralad/ or similar) for the version header comment.
    Affected if The installed version is lower than 1.0.9 or the version cannot be determined (indicating an old release).
  2. Verify the plugin is active
    In WordPress admin, confirm that the ViralAd plugin is currently activated. If the plugin is deactivated, the vulnerability is not reachable.
    Affected if The plugin is activated and running.
  3. Identify the vulnerable code path
    Examine the plugin files for the printResultAndDie() function. Look in the main plugin PHP file for code that uses the 'id' parameter in a database query without prepared statements. Search for patterns like $_GET['id'] or $_REQUEST['id'] being directly inserted into SQL.
    Affected if The printResultAndDie() function exists and uses the 'id' parameter in a raw SQL query without $wpdb->prepare() or equivalent escaping.
  4. Confirm unauthenticated access
    Determine if the vulnerable function is accessible without authentication. Check if the function is called in a file that does not enforce user authentication (such as checks for is_user_logged_in() or current_user_can()).
    Affected if The vulnerable endpoint is reachable without requiring login credentials.

You are affected if the ViralAd plugin is activated, running a version before 1.0.9, and the printResultAndDie() function with the unprotected 'id' parameter is accessible to unauthenticated users.

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 plugin to version 1.0.9 or later once the patch is released. If no update is available, consider removing the plugin or implementing firewall rules at the web application level to block SQL injection attempts on the affected parameter.

Recommended fix Moderate confidence

Version 1.0.9 or later (the first version after 1.0.8)

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the ArielBrailovsky-ViralAd plugin in the list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, deactivate the vulnerable plugin if updates are not available or the plugin is no longer needed.
  6. 6. Verify the update was successful by checking the plugin version number.
Caveat Review plugin functionality after upgrade as minor version updates may include behavior changes

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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