Skip to content
Fencer Intel
medium 6.5

CVE-2023-30943 json

Moodle: tinymce loaders susceptible to arbitrary folder creation

published 3y ago modified 2mo ago also BIT-moodle-2023-30943 , EUVD-2023-1440 , GHSA-22gj-8qj2-fj46

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
6.8%
EPSS 6.8% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

The vulnerability was found Moodle which exists because the application allows a user to control path of the older to create in TinyMCE loaders. A remote user can send a specially crafted HTTP request and create arbitrary folders on the system.

Patch / fix

Is CVE-2023-30943 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 Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-30943 updated cvss 6.5

moodle: TinyMCE loaders susceptible to Arbitrary Folder Creation

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.83% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist moodle/moodle
<4.2.0-rc2
4.2.0-rc2
bitnami moodle
>=4.1.0, <4.1.3
4.1.3

Classification

Weakness
  • CWE-73 External Control of File Name or Path
  • CWE-610 Externally Controlled Reference to a Resource in Another Sphere

References

Sources

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.