CVE-2025-31547
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Aphotrax Uptime Robot Plugin for WordPress uptime-robot-monitor allows SQL Injection.This issue affects Uptime Robot Plugin for WordPress: from n/a through <= 2.3.
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 confidenceSQL Injection vulnerability in the Aphotrax Uptime Robot Plugin for WordPress (uptime-robot-monitor). The plugin fails to properly sanitize user input before using it in SQL queries, allowing attackers to inject malicious SQL commands. Affects versions through 2.3.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the plugin filesCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'uptime-robot-monitor', 'aphotrax-uptime-robot', or similar uptime robot related folder.Affected if The plugin folder exists in the WordPress plugins directory.
-
Determine the installed versionOpen the main plugin PHP file (usually named like uptime-robot-monitor.php) and look for the 'Version:' header in the plugin comment block at the top, or check version info in any included readme.txt file.Affected if The version is 2.3 or lower, or if no version is displayed and the plugin folder is present.
-
Check if the plugin is activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and look for the Uptime Robot monitor plugin in the list. Alternatively, query the wp_options table for option_name = 'active_plugins' and check if the plugin is included.Affected if The plugin is activated on the WordPress site.
-
Identify SQL query usageReview the plugin's PHP files for direct SQL queries using $wpdb->query(), $wpdb->get_results(), or similar without $wpdb->prepare(). Look for instances where user input (like $_POST, $_GET, $_REQUEST, or URL parameters) is concatenated directly into SQL statements.Affected if The plugin contains SQL queries that incorporate user-supplied input without using prepared statements or sanitization functions.
The environment is affected if the Aphotrax Uptime Robot Plugin is installed, active, and running version 2.3 or lower, with direct SQL queries present that use unsanitized user input.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of the plugin. If no patch available, disable the plugin until remediation. For immediate mitigation, review and sanitize all database queries using prepared statements with $wpdb->prepare() or equivalent parameterized queries.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31547 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31547 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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