CVE-2025-60279VulnerabilityPublished 17 Oct 2025

CVE-2025-60279: illia-Builder · n/a

Affects illia-BuilderSource CVE Database V5

Not known to be exploited · CVSS 9.6 Critical : upgrade to 4.8.5 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.6Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.8.5

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade lukehebe/illia-Builder to 4.8.5.

Affected software

Product	Affected	Fixed in
GitHublukehebe/illia-Builder`pkg:github/lukehebe/illia-Builder`Other threats	Affected <4.8.5	Fixed in 4.8.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-60279, European organizations should immediately upgrade illia-Builder to version 4.8.5 or later, where the vulnerability is patched. Until the upgrade is applied, restrict API access to trusted users and networks by implementing strict access controls and network segmentation to limit the ability of authenticated users to reach sensitive internal services. Employ Web Application Firewalls (WAFs) or API gateways with SSRF detection capabilities to monitor and block suspicious outbound requests originating from the illia-Builder API. Conduct thorough internal network monitoring and logging to detect anomalous request patterns indicative of SSRF exploitation attempts. Review and harden internal service configurations to minimize exposure and enforce strict authentication and authorization on internal APIs. Additionally, implement multi-factor authentication (MFA) for all users accessing illia-Builder to reduce the risk of compromised credentials being used to exploit the vulnerability. Regularly audit user privileges to ensure only necessary users have API access. Finally, prepare incident response plans to quickly address any suspected exploitation.

Description

A server-side request forgery (SSRF) vulnerability in Illia Cloud illia-Builder before v4.8.5 allows authenticated users to send arbitrary requests to internal services via the API. An attacker can leverage this to enumerate open ports based on response discrepancies and interact with internal services.

Impact

For European organizations, this vulnerability presents a significant risk, especially for those relying on Illia Cloud illia-Builder for cloud development and deployment workflows. The ability for an authenticated user to perform SSRF attacks can lead to unauthorized internal network reconnaissance, exposing sensitive internal services that are not intended to be publicly accessible. This can facilitate further attacks such as data exfiltration, unauthorized access to internal APIs, or lateral movement to critical systems. The confidentiality and integrity of internal data and services are at high risk, potentially leading to breaches of personal data protected under GDPR, which could result in regulatory fines and reputational damage. The vulnerability does not directly impact availability, but successful exploitation could indirectly cause service disruptions if internal systems are compromised. Given the critical CVSS score, organizations with multi-tenant environments or those hosting sensitive infrastructure behind illia-Builder are particularly vulnerable. The risk is heightened in sectors such as finance, healthcare, and government, where internal network security is paramount and data sensitivity is high.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Oct 2025, 15:47 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats