CVE-2024-36675

CRITICALNVD 9.19.1—Elevated

9.1

LyLme_spage v1.9.5 is vulnerable to Server-Side Request Forgery (SSRF) via the get_head function.

CVSS v3: 9.1
EG Score: 9.1(medium)
EPSS: 97.6%
KEV: Not listed

Published

June 4, 2024

Last Modified

November 21, 2024

References (2)

cve@mitrehttps://github.com/LyLme/lylme_spage/issues/92
af854a3a-2127-422b-91ae-364da2661108https://github.com/LyLme/lylme_spage/issues/92

Weakness Classification(1)

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

CWE-918Server-Side Request Forgery (SSRF)

Data Freshness Timeline

(refreshed 10× in last 7d / 18× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 06:09 UTCepss_batch
2026-06-05 06:09 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-24 00:35 UTCEG score recompute
2026-05-24 00:35 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

Nucleihttp/cves/2024/CVE-2024-36675.yaml
First seen Jan 1, 2024
LyLme spage v1.9.5 - Server-Side Request Forgery
Open source ↗

Frequently asked(5)

What is CVE-2024-36675?

CVE-2024-36675 is a critical vulnerability published on June 4, 2024. LyLmespage v1.9.5 is vulnerable to Server-Side Request Forgery (SSRF) via the gethead function.

When was CVE-2024-36675 disclosed?

CVE-2024-36675 was first published in the National Vulnerability Database on June 4, 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-2024-36675 actively exploited?

CVE-2024-36675 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2024-36675?

CVE-2024-36675 has a CVSS v3 base score of 9.1 (NVD).

How do I remediate CVE-2024-36675?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-36675, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-36675

Explore →

Is Your Infrastructure Affected by CVE-2024-36675?

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

Start Free Scan →Browse All CVEs

CVE-2024-36675

📅 Published

🔄 Last Modified

🔗 References (2)

Weakness Classification(1)

Data Freshness Timeline

Publicly available exploits

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2024-36675?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (2)

Frequently asked(5)

Related CVEs(same CWE)