dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10743

HIGH · 7.5 CVSS v3.1 Published 2025-10-15
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 Outdoor plugin for WordPress is vulnerable to SQL Injection via the 'edit' action in all versions up to, and including, 1.3.2 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 Outdoor WordPress plugin versions up to 1.3.2 contain an unauthenticated SQL Injection vulnerability in the 'edit' action. The vulnerability stems from insufficient escaping of user-supplied parameters combined with a lack of prepared statements in the existing SQL query, allowing attackers to inject arbitrary SQL commands to extract sensitive database information.

MitigationUpdate the Outdoor plugin to the latest version once available, or remove the plugin if no fix is released. Until patched, consider restricting access to the affected endpoint via web server configuration or disabling the plugin entirely.

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. Check Outdoor plugin version
    In WordPress admin, go to Plugins and locate Outdoor to see the installed version, or open wp-content/plugins/outdoor/index.php and read the 'Version' header comment
    Affected if Version is 1.3.2 or lower
  2. Confirm plugin is active
    In WordPress admin, verify the Outdoor plugin shows as active (not deactivated)
    Affected if Plugin is active and version is 1.3.2 or lower
  3. Verify edit action endpoint exists
    Search plugin source code for the 'edit' action handler (look for 'edit' in add_action, do_action, or REST API route definitions). Check if the vulnerable SQL query file is present
    Affected if The edit action code exists and version is 1.3.2 or lower

Your environment is affected if the Outdoor plugin is installed at version 1.3.2 or lower and is currently active, allowing unauthenticated access to the vulnerable edit action.

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 Outdoor plugin to the latest version once available, or remove the plugin if no fix is released. Until patched, consider restricting access to the affected endpoint via web server configuration or disabling the plugin entirely.

Recommended fix Moderate confidence

Outdoor plugin version 1.3.3 or latest available

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Outdoor' plugin
  4. Check the current version number
  5. If the installed version is 1.3.2 or lower, click 'Update Now' to update to the latest version
  6. Alternatively, navigate to Plugins > Add New > Upload and upload a newer version of the plugin
  7. After updating, verify the plugin is running version 1.3.3 or higher

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
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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