Sflog CMS 1.0 Blog Management Interface manage.php unrestricted upload

Summaryinfo

A vulnerability marked as critical has been reported in Sflog CMS 1.0. The affected element is an unknown function of the file manage.php of the component Blog Management Interface. Performing a manipulation results in unrestricted upload. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is identified as CVE-2012-10042. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in Sflog CMS 1.0. It has been classified as critical. This affects an unknown code of the file manage.php of the component Blog Management Interface. The manipulation with an unknown input leads to a unrestricted upload vulnerability. CWE is classifying the issue as CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Sflog! CMS 1.0 contains an authenticated arbitrary file upload vulnerability in the blog management interface. The application ships with default credentials (admin:secret) and allows authenticated users to upload files via manage.php. The upload mechanism fails to validate file types, enabling attackers to upload a PHP backdoor into a web-accessible directory (blogs/download/uploads/). Once uploaded, the file can be executed remotely, resulting in full remote code execution.

The weakness was released by dun. The advisory is shared at raw.githubusercontent.com. This vulnerability is uniquely identified as CVE-2012-10042 since 08/07/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1608.002 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:manage.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Exploit-DB (19626) and EUVD (EUVD-2012-6583). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Sflog

Name

• CMS

Version

• 1.0

Support

• end of life

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion