CVE-2007-4712: eNetman index.php page parameter remote file inclusion

Automated analysis

Generated by VULONE's analysis model from the NVD record, CISA KEV and EPSS data on 19 September 2026. Confidence: medium.

high priorityUnauthenticated remote code execution with a public exploit and very high EPSS score, though the product is old and no KEV listing or active campaign is recorded.

What it is

eNetman 1 contains a remote file inclusion flaw in index.php: the page parameter is used to include a file without validating that it is local. An attacker who can reach the script can point page at a remote URL and cause the server to fetch and execute arbitrary PHP code. The record does not list affected version ranges beyond the product name eNetman 1.

Impact

Successful exploitation gives the attacker arbitrary PHP code execution in the context of the web server, which typically leads to full compromise of the application and any data or host access the web server account holds.

Attack surface

The flaw is reached over the network through HTTP requests to index.php with a crafted page parameter; the CVSS vector AV:N/AC:L/Au:N indicates no authentication and no user interaction are required.

Exploitation

No CISA KEV listing and no ransomware association are recorded, but an Exploit-DB entry (4356) exists and EPSS is 0.57935 (99th percentile), indicating high predicted exploitation activity.

What to do

• Apply the vendor fix or upgrade eNetman to a version that validates the page parameter; no fixed version is stated in this record, so confirm with the vendor.
• If no patch is available, remove or disable index.php or the affected eNetman deployment until it can be remediated.
• Block remote file inclusion by disabling allow_url_include and allow_url_fopen in PHP where the application does not require them.
• Restrict outbound HTTP from the web server and enforce a whitelist of includable files so the page parameter cannot resolve to a remote URL.
• Deploy a WAF rule that rejects page parameter values containing URL schemes or path traversal sequences.

Detection

• Search web server logs for requests to index.php with a page parameter containing http://, https://, ftp:// or other URL schemes.
• Monitor for outbound HTTP connections originating from the web server process to unfamiliar hosts, which would indicate remote include fetching.
• Look for unexpected PHP files or newly written content in web-accessible directories that could be dropped payloads.
• Alert on index.php requests returning 200 with abnormal response sizes or execution errors consistent with included remote code.

This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.