Skip to main content
Public proof of concept

CVE-2024-57438

A public proof of concept exists; no exploitation attested.

  • Published2025-01-29
  • WeaknessCWE-863

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

Insecure permissions in RuoYi v4.8.0 allows authenticated attackers to escalate privileges by assigning themselves higher level roles.

Timeline

dates in UTC
  1. 2025-01-2915:15CVE publishedNVD

Versions per branch

NVD · OSV
Ruoyi
BranchAffectedFixed in
4.8= 4.8.0no fix published
ruoyi
BranchAffectedFixed in
4.8≤ 4.8.0no fix published

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

Fix

No fix published by the sources we read yet. NVD record

Detection

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

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Published
2025-01-29
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-h5jh-rp76-q242

Frequently asked questions

What is CVE-2024-57438?

Insecure permissions in RuoYi v4.8.0 allows authenticated attackers to escalate privileges by assigning themselves higher level roles.

Is CVE-2024-57438 actively exploited?

A proof-of-concept exploit exists for CVE-2024-57438, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2024-57438?

CVE-2024-57438 has a CVSS v3 base score of 5.4 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N.

Running ruoyi? 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