dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10175

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-11
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 WP Links Page plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter in all versions up to, and including, 4.9.6 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 Subscriber-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 · moderate confidence

The WP Links Page WordPress plugin is vulnerable to SQL Injection via the 'id' parameter in versions up to 4.9.6. The vulnerability results from insufficient input escaping combined with lack of prepared statements in the SQL query handling. Authenticated attackers with Subscriber-level access can inject arbitrary SQL queries to extract sensitive data from the database.

MitigationUpdate the plugin to the latest version once a patch is released. Until then, consider disabling the plugin or restricting subscriber-level user registrations if not needed.

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 WP Links Page plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Links Page', or check the wp-content/plugins/ directory for a folder containing 'wp-links-page'
    Affected if Plugin is installed
  2. Determine the installed version
    In the Plugins list, click on the plugin name to reveal the version, or open the main plugin PHP file and read the Version header in the plugin comment block
    Affected if Version is 4.9.6 or lower (any version up to and including 4.9.6)
  3. Confirm the plugin is active
    In WordPress admin > Plugins, check if WP Links Page shows an 'Active' status indicator
    Affected if Plugin is active and running on the site
  4. Identify if subscriber-level access exists
    Go to Users > All Users and review the role column for any users with Subscriber role, or check Settings > General > Membership for 'Anyone can register' with 'Subscriber' selected
    Affected if At least one Subscriber user exists OR subscriber registration is enabled in settings

Environment is affected if WP Links Page plugin is installed, active, at version 4.9.6 or lower, AND subscriber-level user accounts exist or subscriber registration is allowed on the site.

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 the latest version once a patch is released. Until then, consider disabling the plugin or restricting subscriber-level user registrations if not needed.

Recommended fix Moderate confidence

4.9.7 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WP Links Page' plugin
  4. Check the current version - if it is 4.9.6 or earlier, an update is needed
  5. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running version 4.9.7 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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