CVE-2023-0265 json
Uvdesk remote code execution vulnerability
published 3y ago modified 4mo ago also GHSA-2hw6-4rv9-82fp , EUVD-2023-1159
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Uvdesk version 1.1.1 allows an authenticated remote attacker to execute commands on the server. This is possible because the application does not properly validate profile pictures uploaded by customers.
Is CVE-2023-0265 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
1.60% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-15).
Exploits and checks
- fluidattacks.com https://fluidattacks.com/advisories/supply/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | uvdesk/community-skeleton | <=1.1.1 |
no fix listed |
Affected products
- n/a Uvdesk
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
fluidattacks.com
/advisories/supply/
exploit, third-party-advisory
-
github.com
/uvdesk/community-skeleton
package, product
-
nvd.nist.gov
/vuln/detail/CVE-2023-0265
advisory
-
fluidattacks.com
/advisories/supply
web
Sources
- CVE List CVE-2023-0265
- GitHub Advisory GHSA-2hw6-4rv9-82fp
- NVD CVE-2023-0265
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.