VulnerabilityPublished 2 Dec 2025Updated 3 Dec 2025

CVE-2025-65656: dcat-admin · PHP Remote File Inclusion

Affects dcat-adminSource CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

9.8Critical

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

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

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

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Dec 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 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
GitHubjqhph/dcat-admin`pkg:github/jqhph/dcat-admin`Other threats	Affected =2.2.3-beta	Fixed in–

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

AI-suggested

Immediate action should focus on identifying all instances of dcat-admin in the environment, particularly versions 2.2.3-beta and earlier.
Restrict network access to the administrative interface by implementing IP whitelisting or VPN-only access to reduce exposure.
Deploy web application firewalls (WAFs) with custom rules to detect and block file inclusion attack patterns targeting VersionManager.php.
Monitor web server and application logs for suspicious requests that attempt to exploit file inclusion vulnerabilities.
Until an official patch is released, consider disabling or isolating the vulnerable VersionManager.php component if feasible.
Conduct thorough code reviews and penetration testing focused on file inclusion vectors within dcat-admin.
Educate development and operations teams about the risks of file inclusion vulnerabilities and secure coding practices.
Once patches become available, apply them promptly and verify the remediation through testing.
Implement strict input validation and sanitization in custom extensions or configurations of dcat-admin to prevent injection of malicious file paths.
Maintain an incident response plan to quickly address any exploitation attempts or breaches related to this vulnerability.

Description

dcat-admin v2.2.3-beta and before is vulnerable to file inclusion in admin/src/Extend/VersionManager.php.

Impact

The impact of CVE-2025-65656 on European organizations is significant due to the critical severity and ease of exploitation. Successful exploitation can lead to full system compromise, including unauthorized data access, data modification, and service disruption. Confidentiality is at high risk as attackers can access sensitive administrative data. Integrity is compromised because attackers can alter system files or configurations. Availability is threatened through potential denial-of-service conditions or destructive payloads. European organizations that use dcat-admin for managing internal or customer-facing applications may face operational disruptions and reputational damage. The vulnerability could also be leveraged as a foothold for lateral movement within corporate networks. Given the critical CVSS score and no required authentication, attackers can rapidly exploit vulnerable systems, increasing the likelihood of widespread impact. The absence of known exploits in the wild currently provides a limited window for proactive defense, but the risk of imminent exploitation remains high. Organizations in sectors such as finance, government, healthcare, and critical infrastructure in Europe are particularly vulnerable due to their reliance on secure administrative tools and the sensitivity of their data.

CWE-98Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Vulnerable Dependency Management (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.3 (opens in a new tab)
V12.3.6 (opens in a new tab)
V14.2.3 (opens in a new tab)
Attack patterns
PHP Remote File Inclusion (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 9 Dec 2025, 17:54 UTC

WeaknessesCWE-98

Technical details

References

Community reviews

Related threats