CVE-2007-3237
NoneCVSS
—
EPSS
67.7%
Published
Jun 15, 2007
CISA due date
—
Cloudanix analysis
An outdated website module lets attackers run their own programs on the server simply by sending a specially crafted web address.
- Exploitation
- Remote Unauthenticated
- Attacker needs
- None
- Complexity
- Moderate
- Impact
- Remote Code Execution
- Component
- Application
- Class
- RCE
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Remote file inclusion in admin/spaw/spaw_control.class.php allows an unauthenticated attacker to supply an arbitrary URL via the spaw_root parameter, causing the PHP interpreter to fetch and execute attacker-controlled code on the server.
Why it matters to the business
Successful exploitation grants remote code execution on the web server, enabling data theft, website defacement, or use of the server as a pivot for further attacks; the affected module is decades old with no vendor-supplied fixes listed.
How an attack unfolds
An attacker locates a public XOOPS site running the TinyContent 1.5 module, appends a malicious external URL to the spaw_root parameter in a request to admin/spaw/spaw_control.class.php, and the server fetches and executes the remote PHP payload, giving the attacker an interactive shell.
How to fix it
Remove the TinyContent 1.5 module entirely or replace it with a maintained equivalent; if the module must remain, apply third-party patches that neutralize the spaw_root parameter or disable remote URL inclusion in PHP configuration.
How to confirm the fix worked
Inspect the presence of admin/spaw/spaw_control.class.php and test whether supplying an external URL to the spaw_root parameter results in code execution; verify removal or hardening by repeating the same test after changes.
Typical attack path
- Scan or search for XOOPS installations exposing the TinyContent module
- Send crafted HTTP request containing a remote URL in the spaw_root parameter
- Trigger inclusion and execution of attacker-supplied PHP code
- Obtain shell access and perform post-exploitation actions such as credential harvesting or lateral movement
How to detect it
Search web server access logs for requests to spaw_control.class.php that contain the spaw_root parameter with external URLs or unusual schemes; look for resulting PHP processes or file writes originating from the web root.
- spaw_root=
- spaw_control.class.php
- admin/spaw/spaw_control.class.php
What your security team should do
- Immediately audit all public-facing XOOPS deployments for the TinyContent module
- Block or remove the affected module from production environments
- Add web application firewall rules that drop requests containing spaw_root
- Review historical web logs for prior exploitation attempts given the 2007 disclosure date
The record
PHP remote file inclusion vulnerability in admin/spaw/spaw_control.class.php in the TinyContent 1.5 module for XOOPS allows remote attackers to execute arbitrary PHP code via a URL in the spaw_root parameter. NOTE: this issue is probably a duplicate of CVE-2006-4656.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|