dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-9200

HIGH · 7.5 CVSS v3.1 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 →
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 Blappsta Mobile App Plugin – Your native, mobile iPhone App and Android App plugin for WordPress is vulnerable to SQL Injection via the nh_ynaa_comments() function in all versions up to, and including, 0.8.8.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.

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 Blappsta Mobile App Plugin for WordPress contains a SQL Injection vulnerability in the nh_ynaa_comments() function in all versions up to 0.8.8.8. The vulnerability stems from insufficient escaping of user-supplied parameters combined with lack of prepared statements in the SQL query, allowing unauthenticated attackers to inject arbitrary SQL commands and extract sensitive data from the database.

MitigationUpdate the plugin to a patched version above 0.8.8.8 when available, or disable and remove the plugin until a fix is released. If immediate remediation is required, consider restricting access to the affected endpoint via web server configuration.

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. Confirm Blappsta plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Blappsta Mobile App' or check the plugins directory for blappsta files
    Affected if Blappsta plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin > Plugins > Blappsta Mobile App, view the plugin details to see the version number
    Affected if Version is 0.8.8.8 or lower
  3. Identify vulnerable function file
    Locate the plugin files via FTP or file manager, look for files containing 'nh_ynaa_comments' function (typically in main plugin PHP files)
    Affected if The nh_ynaa_comments function exists in the plugin code
  4. Verify endpoint exposure
    Check if the vulnerable endpoint is accessible by reviewing WordPress rewrite rules or testing common paths like /?blappsta_action=comments or similar AJAX endpoints the plugin registers
    Affected if The plugin registers and exposes a publicly accessible endpoint that calls nh_ynaa_comments
  5. Check for recent access logs
    Review web server access logs for requests to any Blappsta-related endpoints that may have triggered the vulnerable function
    Affected if Unauthenticated requests to plugin endpoints appear in logs

A user is affected if the Blappsta Mobile App Plugin version 0.8.8.8 or lower is installed and the plugin's endpoints are publicly accessible.

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

Update the plugin to a patched version above 0.8.8.8 when available, or disable and remove the plugin until a fix is released. If immediate remediation is required, consider restricting access to the affected endpoint via web server configuration.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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