Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2023-54400: Unauthenticated SQL Injection in Fumasoft Fumeng Cloud

Published Sep 29, 2026 · Updated 29 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS9.3Critical · v4
EPSS0.59%49th percentile
CISA KEVNoNot listed
In the wildReported18 exploitation records in Mallory
IdentifiersCVE-2023-54400CWE-89 · Improper Neutralization of Special…

CVE-2023-54400 is an unauthenticated SQL injection vulnerability in Fumasoft Fumeng Cloud. The getEmpByname action improperly handles the Name parameter, allowing remote attackers to inject arbitrary SQL into queries executed against the Microsoft SQL Server backend. UNION-based exploitation can disclose and modify database contents and potentially facilitate further compromise of the underlying server. Exploitation evidence was first observed by the Shadowserver Foundation on October 18, 2023. Specific affected release numbers are not established.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises database confidentiality and integrity by allowing unauthenticated attackers to extract sensitive records and modify stored data. The CVSS assessments also indicate high availability impact. Further compromise of the underlying server is possible, but server-level code execution or an observed server takeover is not established.

Mitigation

If you can’t patch tonight, do this now.

Apply strict validation to the Name parameter and restrict the application's database account to the minimum necessary permissions. These measures can reduce exposure and limit exploitation impact but do not replace parameterized queries.

Remediation

Patch, then assume compromise.

Replace SQL query construction involving the Name parameter with parameterized queries or prepared statements, and enforce strict input validation. A vendor-fixed release or specific upgrade target is not identified in the available information.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2023-54400 exploited in the wild?
Yes. As of Oct 24, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2023-54400?
Yes. As of Oct 24, 2026, Mallory has reports of a public exploit for CVE-2023-54400.
Is there a patch for CVE-2023-54400?
Replace SQL query construction involving the Name parameter with parameterized queries or prepared statements, and enforce strict input validation. A vendor-fixed release or specific upgrade target is not identified in the available information.
How severe is CVE-2023-54400?
CVE-2023-54400 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 0.59% (49th percentile) as of Oct 24, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.