VulnerabilityPublished 27 Jun 2025

CVE-2025-52207: MIKO MikoPBX · Relative Path Traversal

Affects MIKO MikoPBXSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 9.9 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

9.9Critical

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

EPSS: 1.6% chance of exploitation in 30 days – higher than 75% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jun 2025
Detectable: evidence found.
nuclei template: MikoPBX - Unrestricted File Upload
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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
MIKO MikoPBX	Affected =0	Fixed in–

AI-suggested

To mitigate the risks posed by CVE-2025-52207, European organizations should implement the following specific measures: 1) Immediately restrict access to the MikoPBX management interfaces to trusted IP addresses and networks using firewall rules and network segmentation to reduce exposure. 2) Enforce strict privilege management to ensure only highly trusted users have access to the vulnerable upload functionality, minimizing the risk of exploitation by insiders or compromised accounts. 3) Monitor web server directories and file upload locations for unauthorized PHP or script files, employing file integrity monitoring tools to detect suspicious changes promptly. 4) Implement Web Application Firewalls (WAFs) with custom rules to detect and block path traversal attempts and suspicious file uploads targeting the PBXCoreREST API endpoints. 5) Regularly audit and review logs for unusual activities related to file uploads or access to the PostController.php endpoint. 6) Engage with MIKO for timely patching once updates become available and prioritize deployment of security updates. 7) As an interim measure, consider disabling or restricting the vulnerable upload functionality if feasible without disrupting business operations. 8) Conduct penetration testing and vulnerability assessments focused on telephony infrastructure to identify and remediate similar weaknesses.

Description

PBXCoreREST/Controllers/Files/PostController.php in MikoPBX through 2024.1.114 allows uploading a PHP script to an arbitrary directory.

Impact

For European organizations, the impact of CVE-2025-52207 could be severe, especially for enterprises and service providers relying on MikoPBX for telephony infrastructure. Compromise of PBX systems can lead to interception of sensitive voice communications, unauthorized call routing, toll fraud, and disruption of business communications. Given the critical nature of the vulnerability, attackers could gain persistent access to internal networks, potentially leading to broader data breaches or ransomware attacks. Industries such as finance, healthcare, government, and telecommunications in Europe are particularly at risk due to their reliance on secure and reliable communication systems. Additionally, the exposure of internal communications could violate GDPR regulations, leading to legal and financial penalties. The ability to upload arbitrary PHP scripts without user interaction and with low complexity means that even moderately skilled attackers could exploit this vulnerability remotely, increasing the threat landscape for European organizations.

CWE-23Relative Path Traversal (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
Operation · Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Relative Path Traversal (opens in a new tab)
Manipulating Web Input to File System Calls (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 27 Jun 2025, 17:24 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-23

Technical details

References

Community reviews

Related threats