dbcve.org
Backend LocalizationWordPress extension · Kau Boys

CVE-2023-44471

HIGH · 8.8 CVSS v3.1 Published 2023-10-10
Fix available
A fix is available. Upgrade to after 2.1.10 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Bernhard Kau Backend Localization plugin <= 2.1.10 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Bernhard Kau Backend Localization WordPress plugin versions 2.1.10 and below allows attackers to induce authenticated administrators to perform unintended actions by tricking them into visiting malicious URLs.

MitigationUpdate the Bernhard Kau Backend Localization plugin to the latest version (currently 2.1.11 or later) which contains the CSRF protection fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Backend LocalizationWordPress extension
Affected:<= 2.1.10

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 Backend Localization plugin
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Kau Boys Backend Localization' or 'Backend Localization' by Bernhard Kau
    Affected if The plugin is installed and active on the WordPress site
  2. Identify the installed version
    On the Plugins page, find the plugin and note the version number displayed below the plugin name, or open the main plugin file (typically /wp-content/plugins/backend-localization/includes/class-backend-localization.php or similar) and check the 'Version' header in the plugin comment block
    Affected if The displayed version is 2.1.10 or lower, or no version number is shown and the plugin appears unpatched
  3. Verify the CSRF protection is absent
    If possible, examine the plugin source code for anti-CSRF tokens (look for nonces, wp_nonce_field, or check_admin_referer function calls) in files handling form submissions or URL redirects, particularly in admin settings pages
    Affected if No nonce verification or referer checks are found in the plugin's form handling or action processing code

You are affected if the Kau Boys Backend Localization plugin is installed with version 2.1.10 or lower, as this version lacks CSRF protection mechanisms.

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
Upgrade available Upgrade to a release after 2.1.10
Interim mitigation

Update the Bernhard Kau Backend Localization plugin to the latest version (currently 2.1.11 or later) which contains the CSRF protection fix.

Recommended fix Moderate confidence

Update to the latest version available in the WordPress plugin repository (version higher than 2.1.10)

  1. 1. Check the current installed version of the Backend Localization plugin in your WordPress installation
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Backend Localization plugin by Bernhard Kau
  4. 4. If the installed version is 2.1.10 or lower, update to the latest available version from the WordPress plugin repository
  5. 5. After updating, verify the new version number reflects the update was successful
  6. 6. Confirm the plugin functions correctly after the update

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

Fix this in Backend Localization Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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