dbcve.org
Kb SupportWordPress extension · Logon

CVE-2023-25983

HIGH · 8.8 CVSS v3.1 Published 2023-11-07
Fix available
A fix is available. Upgrade to after 1.5.85 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Improper Neutralization of Formula Elements in a CSV File vulnerability in WPOmnia KB Support.This issue affects KB Support: from n/a through 1.5.84.

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

This is a CSV injection vulnerability in the KB Support WordPress plugin where exported CSV files don't properly sanitize formula characters (=, +, -, @). Attackers can inject malicious formulas that execute when users open the CSV in spreadsheet software, potentially leading to command execution or data exfiltration.

MitigationUpgrade KB Support to version 1.5.85 or later. If upgrade is not possible, implement output encoding for CSV exports by prefixing formula characters with a single quote or filtering them entirely.

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
Kb SupportWordPress extension
Affected:<= 1.5.85

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify KB Support plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'KB Support' or check the /wp-content/plugins/kb-support/ directory exists on the server
    Affected if KB Support plugin is present on the WordPress site
  2. Check installed version number
    In WordPress admin, go to Plugins > Installed Plugins, find KB Support, and note the version number displayed below the plugin name. Alternatively, check the version in the plugin's main PHP file header or readme.txt
    Affected if Version is 1.5.85 or lower (the vulnerability is present in versions up to and including 1.5.85)
  3. Identify CSV export functionality
    Navigate to the KB Support plugin settings and locate any ticket export, report export, or data export features that generate CSV files. Common paths: Tickets > Export or Settings > Import/Export
    Affected if CSV export feature exists and is accessible to users
  4. Test CSV output for formula injection
    Create a test ticket with a subject or description containing formula characters (e.g., =1+1, +2-2, -3+3, @test) and export to CSV using the plugin's export function. Open the resulting CSV in a spreadsheet application and observe if formulas execute or display alert messages
    Affected if Formula characters are not escaped (appearing as =, +, -, @ without preceding single quote) and execute when opened in spreadsheet software

A user is affected if the KB Support plugin version is 1.5.85 or lower AND the CSV export feature is accessible on their WordPress 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
Upgrade available Upgrade to a release after 1.5.85
Interim mitigation

Upgrade KB Support to version 1.5.85 or later. If upgrade is not possible, implement output encoding for CSV exports by prefixing formula characters with a single quote or filtering them entirely.

Recommended fix Moderate confidence

Upgrade to KB Support version 1.5.85 or later (latest stable release)

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate KB Support (WPOmnia) in the plugin list
  4. Check if an update is available for KB Support
  5. If an update is available, click 'Update Now' to install the latest version
  6. After updating, verify the plugin version is 1.5.85 or higher to confirm the vulnerability is patched
  7. If no automatic update is available, manually download the latest version from the WordPress plugin repository or WPOmnia and upload it via Plugins > Add New > Upload Plugin

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

Fix this in Kb Support 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 the upgrade done

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-2023-25983 — 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-25983 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