What is the CVSS score of CVE-2025-34100?

CVE-2025-34100 has a CVSS 4.0 base score of 9.3 (Critical). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. EPSS exploitation probability: 67.4%.

Which versions of PHP are affected by CVE-2025-34100?

BuilderEngine 3.5.0 contains a critical remote code execution vulnerability that allows unauthenticated attackers to upload and execute malicious code on affected servers.

Is there a public PoC exploit available for CVE-2025-34100?

Yes, a public proof-of-concept exploit is available for CVE-2025-34100. Prioritise patching immediately. EPSS: 67.4%.

How to fix or mitigate CVE-2025-34100?

Within 24 hours: Immediately take BuilderEngine instances offline or restrict network access to trusted IPs only; audit logs for signs of exploitation. Within 7 days: Evaluate alternative website builders or request emergency patched version from vendor; implement Web Application Firewall rules to block suspicious file uploads. Within 30 days: Complete migration to patched version or replacement solution; conduct forensic analysis of systems for backdoors or data exfiltration.

PHP CVE-2025-34100

EUVD-2025-21028 CRITICAL

Improper Input Validation (CWE-20)

2025-07-10 disclosure@vulncheck.com

PHP RCE Jquery Authentication Bypass

9.3

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

9.3 CRITICAL

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Lifecycle Timeline

EUVD ID Assigned

Mar 16, 2026 - 06:52 euvd

EUVD-2025-21028

Analysis Generated

Mar 16, 2026 - 06:52 vuln.today

PoC Detected

Jul 15, 2025 - 13:14 vuln.today

Public exploit code

CVE Published

Jul 10, 2025 - 20:15 nvd

CRITICAL 9.3

DescriptionCVE.org

An unrestricted file upload vulnerability exists in BuilderEngine 3.5.0 via the integration of the elFinder 2.0 file manager and its use of the jQuery File Upload plugin. The plugin fails to properly validate or restrict file types or locations during upload operations, allowing an attacker to upload a malicious .php file and subsequently execute arbitrary PHP code on the server under the context of the web server process. While the root vulnerability lies within the jQuery File Upload component, BuilderEngine’s improper integration and lack of access controls expose this functionality to unauthenticated users, resulting in full remote code execution.

AnalysisAI

BuilderEngine 3.5.0 contains a critical unrestricted file upload vulnerability in its elFinder 2.0 integration and jQuery File Upload plugin, allowing unauthenticated attackers to upload and execute arbitrary PHP files on the server, resulting in complete remote code execution (RCE) under the web server process context. The vulnerability is characterized by a CVSS 9.3 score with no authentication or user interaction required, making it immediately exploitable across network boundaries.

Technical ContextAI

The vulnerability stems from improper input validation (CWE-20: Improper Input Validation) in the jQuery File Upload plugin as integrated into BuilderEngine's elFinder 2.0 file manager component. The root cause is the failure to enforce file type whitelisting, extension validation, and upload directory restrictions. The jQuery File Upload plugin, designed for legitimate client-side file uploads, lacks server-side verification of MIME types and file extensions when integrated into BuilderEngine without proper access controls. BuilderEngine fails to restrict upload endpoints to authenticated users, exposing the vulnerable jQuery File Upload handler to unauthenticated requests. The combination allows attackers to POST a malicious .php file to the upload endpoint, which is stored in a web-accessible directory and subsequently executed via direct HTTP requests, executing arbitrary PHP code in the context of the web server process (typically www-data or apache user).

RemediationAI

Immediate actions: (1) Patch to a patched BuilderEngine version if available from the vendor (3.5.1+)—verify vendor advisory for confirmed patch release; (2) If patching is not immediately feasible, implement emergency mitigations: disable or restrict access to file upload endpoints at the web server level (nginx/Apache) using IP whitelisting or authentication middleware; (3) Implement strict server-side file upload validation: enforce whitelist of permitted MIME types (not blacklist), validate file extensions server-side, store uploads outside web root or in a directory with PHP execution disabled (.htaccess: php_flag engine off), enforce Content-Type header verification; (4) Review elFinder 2.0 and jQuery File Upload configurations for security settings; (5) Apply principle of least privilege to web server process; (6) Monitor upload directories and access logs for suspicious .php file uploads; (7) Implement Web Application Firewall (WAF) rules to block PHP file uploads or .php execution in upload directories; (8) Conduct comprehensive audit of all file upload functionality within BuilderEngine for similar validation gaps.