dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-11177

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 External Login plugin for WordPress is vulnerable to SQL Injection via the 'log' parameter in all versions up to, and including, 1.11.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 when a PostgreSQL or MSSQL database is configured as the external authentication 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 External Login WordPress plugin versions up to 1.11.2 contain an unauthenticated SQL injection vulnerability in the 'log' parameter. Due to insufficient escaping of user input and lack of prepared statements in the SQL query, attackers can append malicious SQL commands. This is only exploitable when PostgreSQL or MSSQL is configured as the external authentication database, as these databases handle SQL concatenation differently than MySQL.

MitigationUpdate the External Login plugin to the latest patched version once released. If immediate patching is not possible, consider disabling the plugin or implementing WAF rules to block SQL injection attempts targeting the 'log' parameter.

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. Locate the External Login plugin and identify its version
    Access the WordPress wp-content/plugins/ directory and locate the external-login plugin folder. Open the main plugin PHP file (typically external-login.php) and look for the version declaration in the plugin header comment, or check the readme.txt file for the Version field.
    Affected if The installed version is 1.11.2 or any earlier version (the plugin version is at or below 1.11.2).
  2. Verify the external authentication database type
    Examine the WordPress configuration (wp-config.php) and the External Login plugin settings to determine which database type is configured for the external authentication connection. Look for database connection parameters that specify PostgreSQL or MSSQL.
    Affected if The external authentication database is configured as PostgreSQL or MSSQL (this vulnerability does not apply when using MySQL).
  3. Confirm the plugin is active with external database configured
    Check the WordPress admin plugin status to confirm the External Login plugin is enabled, then review the plugin configuration to verify that an external authentication database connection is actually configured and in use.
    Affected if The plugin is active and has an external PostgreSQL or MSSQL authentication database configured and connected.

A user is affected if they have the External Login plugin installed at version 1.11.2 or lower AND have PostgreSQL or MSSQL configured as their external authentication database, with the plugin active and the external auth feature enabled.

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 External Login plugin to the latest patched version once released. If immediate patching is not possible, consider disabling the plugin or implementing WAF rules to block SQL injection attempts targeting the 'log' parameter.

Recommended fix High confidence

External Login plugin version 1.11.3 or higher

  1. 1. Update the External Login WordPress plugin to version 1.11.3 or later through the WordPress admin dashboard (Plugins > Updates Available), or
  2. 2. If automatic updates are not enabled, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org/plugins/external-login/, or
  3. 3. Alternatively, download the latest version from wordpress.org and manually upload via FTP or the WordPress file manager

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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