dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10652

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Robcore Netatmo plugin for WordPress is vulnerable to SQL Injection via the ‘module_id’ attribute of the robcore-netatmo shortcode in all versions up to, and including, 1.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, 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 Robcore Netatmo WordPress plugin fails to properly escape the 'module_id' parameter in the robcore-netatmo shortcode and lacks prepared statements in its SQL queries. This allows authenticated users with Contributor-level access or higher to inject arbitrary SQL commands via the module_id attribute, potentially exposing sensitive database information.

MitigationUpdate the Robcore Netatmo plugin to version 1.8 or later, which addresses the SQL injection vulnerability. If immediate update is not possible, restrict shortcode usage permissions pending the 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Robcore Netatmo plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Robcore Netatmo' or check the plugins directory for robcore-netatmo folder
    Affected if plugin is present and active
  2. Check installed plugin version
    In WordPress admin Plugins list, click on the plugin to view details, or inspect the main plugin file header for 'Version' value. Compare to 1.8.
    Affected if version is less than 1.8 (e.g., 1.7, 1.6, etc.)
  3. Identify shortcode usage
    Search posts, pages, and widgets for the [robcore-netatmo] shortcode, or check theme files for do_shortcode calls with this tag
    Affected if shortcode is present in published content
  4. Review user role permissions
    In WordPress admin Users section, verify which roles have Contributor-level or higher access, as these roles can use the vulnerable shortcode
    Affected if Contributor or higher roles exist and shortcode is in use

Your environment is affected if the Robcore Netatmo plugin version is below 1.8 AND the robcore-netatmo shortcode is accessible to users with Contributor-level permissions or higher.

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 Robcore Netatmo plugin to version 1.8 or later, which addresses the SQL injection vulnerability. If immediate update is not possible, restrict shortcode usage permissions pending the patch.

Recommended fix Moderate confidence

Version 1.8 or later of the Robcore Netatmo plugin

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Robcore Netatmo plugin
  4. Check the current version installed (should be 1.7 or below)
  5. Update the plugin to version 1.8 or later
  6. Verify the update was successful by checking the plugin version
Caveat No known breaking changes reported for this update; this is a security patch

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

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-10652 — 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-10652 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