dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-0745

MEDIUM · 5.5 CVSS v3.1 Published 2026-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/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 User Language Switch plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.6.10 due to missing URL validation on the 'download_language()' function. This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 User Language Switch WordPress plugin versions up to 1.6.10 contain a Server-Side Request Forgery (SSRF) vulnerability in the download_language() function due to missing URL validation. Authenticated administrators can cause the application to make arbitrary HTTP requests to internal or external resources.

MitigationUpdate the User Language Switch plugin to version 1.6.11 or later which implements proper URL validation on the download_language() function to prevent SSRF attacks.

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
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/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 User Language Switch plugin is installed
    Navigate to WordPress Admin > Plugins > Installed Plugins and look for 'User Language Switch' in the list, or check the /wp-content/plugins/ directory for a folder named 'user-language-switch' or similar.
    Affected if The plugin appears in the installed plugins list regardless of activation status
  2. Check the installed plugin version
    In WordPress Admin > Plugins, click 'View Details' on the User Language Switch plugin to display the version number from the plugin header, or open the main plugin PHP file (e.g., user-language-switch.php) and locate the 'Version' field in the plugin header comment.
    Affected if The version number displayed is 1.6.10 or lower
  3. Confirm administrator accounts exist
    In WordPress Admin > Users, verify that at least one user with the Administrator role exists. Alternatively, query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'administrator'.
    Affected if One or more administrator-level accounts are present in the WordPress installation
  4. Check for access to the vulnerable download_language function
    Examine the plugin source code for the download_language() function and identify any AJAX hooks, admin menu pages, or REST API endpoints that call it. Look for wp_ajax_ or admin_action hooks referencing 'download_language' or similar patterns.
    Affected if The download_language function is hooked to an accessible WordPress action or endpoint accessible to administrators

A user is affected if the User Language Switch plugin is installed with version 1.6.10 or lower and the site has at least one administrator account, since the SSRF vulnerability can be exploited by authenticated administrators through the download_language() function.

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 User Language Switch plugin to version 1.6.11 or later which implements proper URL validation on the download_language() function to prevent SSRF attacks.

Recommended fix Moderate confidence

User Language Switch version 1.6.11 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'User Language Switch' plugin
  4. Click 'Update now' if an update is available, or manually upload version 1.6.11 or later
  5. Verify the plugin version after update to confirm the patch is applied

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-2026-0745 — 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-2026-0745 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