Skip to main content
No exploitation reportedFix available

CVE-2023-1800

No exploitation reported by the sources we read.

  • Published2023-04-02
  • Fixed in1.4.5-0.20230408141131-61cbff5124c6
  • WeaknessCWE-24 · CWE-434

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A vulnerability, which was classified as critical, has been found in sjqzhang go-fastdfs up to 1.4.3. Affected by this issue is the function upload of the file /group1/uploa of the component File Upload Handler. The manipulation leads to path traversal: '../filedir'. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-224768.

Timeline

dates in UTC
  1. 2023-04-0211:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-03 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-1800?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-1800?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV · NVD
sjqzhang/go-fastdfs
BranchAffectedFixed in
1.4< 1.4.5-0.20230408141131-61cbff5124c61.4.5-0.20230408141131-61cbff5124c6
Go-fastdfs project go-fastdfs
BranchAffectedFixed in
1.4≤ 1.4.3no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As VulDB, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • sjqzhang go-fastdfs
    Affected
    • = 1.4.0no fix stated
    • = 1.4.1no fix stated
    • = 1.4.2no fix stated
    • = 1.4.3no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-02-13

Fix

  1. Update sjqzhang/go-fastdfs to 1.4.5-0.20230408141131-61cbff5124c6

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2024-11-22
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.17.3known since 2026-10-23
  • NVDCVSS 3.19.8read 2026-10-23
  • CNACVSS 2.07.5known since 2026-10-23
  • CNAweakness (CWE)CWE-24known since 2026-10-23
  • NVDweakness (CWE)CWE-434read 2026-10-23
  • FIRST EPSSEPSS score3.6 %2026-11-03
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryCRITICAL2023-04-07

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2023-04-02
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-xq3x-grrj-fj6x

Frequently asked questions

What is CVE-2023-1800?

A vulnerability, which was classified as critical, has been found in sjqzhang go-fastdfs up to 1.4.3. Affected by this issue is the function upload of the file /group1/uploa of the component File Upload Handler. The manipulation leads to path traversal: '../filedir'. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-224768.

Is CVE-2023-1800 actively exploited?

Active exploitation of CVE-2023-1800 has not been confirmed. Its EPSS score was 3.6% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-1800?

CVE-2023-1800 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running sjqzhang/go-fastdfs? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record