CVE-2023-47115

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 1.4% (72nd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 7.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Label Studio is an a popular open source data labeling tool. Versions prior to 1.9.2 have a cross-site scripting (XSS) vulnerability that could be exploited when an authenticated user uploads a crafted image file for their avatar that gets rendered as a HTML file on the website. Executing arbitrary JavaScript could result in an attacker performing malicious actions on Label Studio users if they visit the crafted avatar image. For an example, an attacker can craft a JavaScript payload that adds a new Django Super Administrator user if a Django administrator visits the image.

The file users/functions.py lines 18-49 show that the only verification check is that the file is an image by extracting the dimensions from the file. Label Studio serves avatar images using Django's built-in serve view, which is not secure for production use according to Django's documentation. The issue with the Django serve view is that it determines the Content-Type of the response by the file extension in the URL path. Therefore, an attacker can upload an image that contains malicious HTML code and name the file with a .html extension to be rendered as a HTML page. The only file extension validation is performed on the client-side, which can be easily bypassed.

Version 1.9.2 fixes this issue. Other remediation strategies include validating the file extension on the server side, not in client-side code; removing the use of Django's serve view and implement a secure controller for viewing uploaded avatar images; saving file content in the database rather than on the filesystem to mitigate against other file related vulnerabilities; and avoiding trusting user controlled inputs.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.4%
EPSS %ILE
72nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 23, 2024

Last Modified

November 21, 2024

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
label-studio0.4.1 ... 1.9.1.post0 (74 versions)
  • every version up to 1.9.2: fixed in 1.9.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 186 total refreshes for this CVE.

  1. 2026-10-10 19:57 UTCEPSS rescore
  2. 2026-10-09 20:05 UTCEPSS rescore
  3. 2026-10-08 17:06 UTCEPSS rescore
  4. 2026-10-07 23:46 UTCEPSS rescore
  5. 2026-10-06 15:15 UTCEPSS rescore
  6. 2026-10-05 17:41 UTCEPSS rescore
  7. 2026-10-04 23:20 UTCEPSS rescore
  8. 2026-10-03 14:23 UTCEPSS rescore
  9. 2026-10-01 19:48 UTCEPSS rescore
  10. 2026-09-30 16:33 UTCEG score recompute
  11. 2026-09-30 15:01 UTCEPSS rescore
  12. 2026-09-29 15:17 UTCEPSS rescore
  13. 2026-09-28 13:49 UTCEPSS rescore
  14. 2026-09-27 13:42 UTCEPSS rescore
  15. 2026-09-26 00:22 UTCEPSS rescore
  16. 2026-09-24 14:01 UTCEPSS rescore
  17. 2026-09-24 14:01 UTCEPSS rescore
  18. 2026-09-23 13:46 UTCEPSS rescore
  19. 2026-09-22 14:46 UTCEPSS rescore
  20. 2026-09-22 09:46 UTCOSV refresh
  21. 2026-09-21 20:31 UTCEPSS rescore
  22. 2026-09-20 20:14 UTCEPSS rescore
  23. 2026-09-20 20:14 UTCEPSS rescore
  24. 2026-09-18 19:26 UTCEPSS rescore
  25. 2026-09-17 19:25 UTCEPSS rescore
Show 75 more
  1. 2026-09-16 14:06 UTCEPSS rescore
  2. 2026-09-16 05:11 UTCEPSS rescore
  3. 2026-09-15 03:08 UTCEPSS rescore
  4. 2026-09-13 16:44 UTCEPSS rescore
  5. 2026-09-12 14:58 UTCEPSS rescore
  6. 2026-09-11 14:50 UTCEPSS rescore
  7. 2026-09-11 09:34 UTCEPSS rescore
  8. 2026-09-08 21:58 UTCEPSS rescore
  9. 2026-09-07 15:59 UTCEPSS rescore
  10. 2026-09-06 13:46 UTCEPSS rescore
  11. 2026-09-06 13:45 UTCEPSS rescore
  12. 2026-09-05 15:26 UTCEPSS rescore
  13. 2026-09-04 13:58 UTCEPSS rescore
  14. 2026-09-04 05:04 UTCEPSS rescore
  15. 2026-09-03 07:00 UTCOSV refresh
  16. 2026-09-02 14:10 UTCEPSS rescore
  17. 2026-09-02 14:09 UTCEPSS rescore
  18. 2026-09-01 13:51 UTCEPSS rescore
  19. 2026-09-01 04:35 UTCEPSS rescore
  20. 2026-08-30 19:15 UTCEPSS rescore
  21. 2026-08-30 01:20 UTCEPSS rescore
  22. 2026-08-28 21:39 UTCEPSS rescore
  23. 2026-08-27 14:23 UTCEPSS rescore
  24. 2026-08-26 14:44 UTCEPSS rescore
  25. 2026-08-25 13:46 UTCEPSS rescore
  26. 2026-08-24 14:14 UTCEPSS rescore
  27. 2026-08-23 00:17 UTCEPSS rescore
  28. 2026-08-21 23:47 UTCEPSS rescore
  29. 2026-08-20 22:53 UTCEPSS rescore
  30. 2026-08-19 17:02 UTCEPSS rescore
  31. 2026-08-19 17:02 UTCEPSS rescore
  32. 2026-08-18 13:46 UTCEPSS rescore
  33. 2026-08-17 13:45 UTCEPSS rescore
  34. 2026-08-16 20:56 UTCOSV refresh
  35. 2026-08-16 14:54 UTCEPSS rescore
  36. 2026-08-16 02:12 UTCEPSS rescore
  37. 2026-08-15 01:28 UTCEPSS rescore
  38. 2026-08-13 21:58 UTCEPSS rescore
  39. 2026-08-12 13:49 UTCEPSS rescore
  40. 2026-08-11 13:40 UTCEPSS rescore
  41. 2026-08-10 23:57 UTCEPSS rescore
  42. 2026-08-09 13:44 UTCEPSS rescore
  43. 2026-08-09 13:44 UTCEPSS rescore
  44. 2026-08-08 16:35 UTCEPSS rescore
  45. 2026-08-07 16:25 UTCEPSS rescore
  46. 2026-08-06 13:45 UTCEPSS rescore
  47. 2026-08-05 19:15 UTCEPSS rescore
  48. 2026-08-04 15:07 UTCEPSS rescore
  49. 2026-08-04 10:35 UTCEPSS rescore
  50. 2026-08-03 10:34 UTCEPSS rescore
  51. 2026-08-03 10:34 UTCEPSS rescore
  52. 2026-08-02 02:25 UTCEPSS rescore
  53. 2026-08-02 02:25 UTCEPSS rescore
  54. 2026-08-01 14:36 UTCOSV refresh
  55. 2026-08-01 04:14 UTCEPSS rescore
  56. 2026-07-30 16:26 UTCEPSS rescore
  57. 2026-07-30 16:26 UTCEPSS rescore
  58. 2026-07-30 01:28 UTCEPSS rescore
  59. 2026-07-28 15:34 UTCEPSS rescore
  60. 2026-07-28 15:34 UTCEPSS rescore
  61. 2026-07-26 14:52 UTCEPSS rescore
  62. 2026-07-25 14:16 UTCEPSS rescore
  63. 2026-07-24 14:16 UTCEPSS rescore
  64. 2026-07-24 14:16 UTCEPSS rescore
  65. 2026-07-23 14:16 UTCEPSS rescore
  66. 2026-07-23 02:27 UTCEG score recompute
  67. 2026-07-22 23:14 UTCEG score recompute
  68. 2026-07-22 14:06 UTCEPSS rescore
  69. 2026-07-21 15:23 UTCEPSS rescore
  70. 2026-07-21 15:23 UTCEPSS rescore
  71. 2026-07-20 17:06 UTCEPSS rescore
  72. 2026-07-19 14:29 UTCEPSS rescore
  73. 2026-07-19 14:29 UTCEPSS rescore
  74. 2026-07-19 02:27 UTCEPSS rescore
  75. 2026-07-18 10:03 UTCEPSS rescore

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2023/CVE-2023-47115.yaml
    Published Jan 30, 2024

    Label Studio - Cross-Site Scripting

    Open source ↗

Frequently asked(5)

What is CVE-2023-47115?
CVE-2023-47115 is a high vulnerability published on January 23, 2024. Label Studio is an a popular open source data labeling tool. Versions prior to 1.9.2 have a cross-site scripting (XSS) vulnerability that could be exploited when an authenticated user uploads a crafted image file for their avatar that gets rendered as a HTML file on the website. Executing arbitrary…
When was CVE-2023-47115 disclosed?
CVE-2023-47115 was first published on January 23, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-47115 actively exploited?
CVE-2023-47115 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-47115?
CVE-2023-47115 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2023-47115?
A fix for CVE-2023-47115 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-47115

Explore →

Is Your Infrastructure Affected by CVE-2023-47115?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.