NVD / CVE Program· CNA @huntrdev

CVE-2023-0455: Unrestricted Upload of File with Dangerous Type in unilogies/bumsys

Noroxi assessment

Priority: Monitor (action score 37/100)

Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 5.7% (FIRST EPSS); higher than 93% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
No fixed version is recorded, but the references include a patch (commit or PR) link.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. See the fix and affected versions sections below.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Unrestricted Upload of File with Dangerous Type in GitHub repository unilogies/bumsys prior to v1.0.3-beta.

HighCVSS 8.8 · v3.1—Proof of concept No fix recorded

File upload

Published: Jan 26, 2023
Updated: Jun 17, 2026
EPSS: 5.7% · 93th percentile
CWE: CWE-434

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 2 / 30 · 5.7%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 8.8
CNA · @huntrdev: 7.6; 1.2 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
bumsys project	bumsys	cpe:2.3:a:bumsys_project:bumsys

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

bumsys project bumsys1.0.0
bumsys project bumsys1.0.1
bumsys project bumsys1.0.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (@huntrdev). Independent of NVD's CPE analysis and usually ahead of it.

unilogies unilogies/bumsys
- unspecified and later · before v1.0.3-betaaffected

Same product

bumsys project: all records

Other highest-scoring records for the same primary product.

CVE-2023-2554External Control of File Name or Path in unilogies/bumsys
37Monitor
CVE-2023-2551PHP Remote File Inclusion in unilogies/bumsys
36Monitor
CVE-2023-2552Cross-Site Request Forgery (CSRF) in unilogies/bumsys
35Monitor

Published before and after this one in the same product

Later →CVE-2023-1361Mar 13, 2023 · SQL Injection in unilogies/bumsys
26Monitor
Later →CVE-2023-1362Mar 13, 2023 · Improper Restriction of Rendered UI Layers or Frames in unilogies/bumsys
24Monitor
Later →CVE-2023-2553May 5, 2023 · Cross-site Scripting (XSS) - Stored in unilogies/bumsys
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Exploit-DB entry ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Exploit-DB entry	webapps	2023-05-31

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedJan 26, 2023
First PoCMay 31, 2023+124 d
TodayOct 27, 2026+1370 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

unilogies/bumsyscommit a5beff7

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).