CVE-2024-7058: Relative Path Traversal in parisneo/lollms-webui
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
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
A vulnerability in the sanitize_path function in parisneo/lollms-webui v10 - latest allows an attacker to bypass path sanitization by using relative paths such as './'. This can lead to unauthorized access to directories within the personality_folder on the victim's computer.
- Published
- Mar 20, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- CWE-23
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · @huntr_ai
- 4.4
- NVD has not scored this yet; the score shown is the CNA’s.
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
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 helpAffected 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 |
|---|---|---|
| lollms | lollms web ui | cpe:2.3:a:lollms:lollms_web_ui |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lollms lollms web ui10
Versions reported by the vendor
Affected version ranges reported by the assigning authority (@huntr_ai). Independent of NVD's CPE analysis and usually ahead of it.
parisneo parisneo/lollms
- unspecified and later · up to and including latestaffected
Same product
lollms: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-1520OS Command Injection in parisneo/lollms-webui53Plan
- CVE-2024-4320Remote Code Execution due to LFI in '/install_extension' in parisneo/lollms-webui49Plan
- CVE-2024-1600Local File Inclusion in parisneo/lollms-webui47Plan
Published before and after this one in the same product
- ← EarlierCVE-2024-12766Mar 20, 2025 · SSRF in parisneo/lollms-webui30Monitor
- ← EarlierCVE-2024-6986Mar 20, 2025 · Cross-site Scripting (XSS) in parisneo/lollms-webui21Monitor
- Later →CVE-2024-8581Mar 20, 2025 · Path Traversal in parisneo/lollms-webui36Monitor
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
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, 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.
- CVE-2024-4330294 days apartPath Traversal in parisneo/lollms-webui13Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2024-99190 days apartMissing Authentication Check in parisneo/lollms-webui33Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-23 · Relative Path TraversalCVSS vector
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.