dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2012-10044

CRITICAL · 10.0 CVSS v4.0 Published 2025-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MobileCartly version 1.0 contains an arbitrary file creation vulnerability in the savepage.php script. The application fails to perform authentication or authorization checks before invoking file_put_contents() on attacker-controlled input. An unauthenticated attacker can exploit this flaw by sending crafted HTTP GET requests to savepage.php, specifying both the filename and content. This allows arbitrary file creation within the pages/ directory or any writable path on the server, allowing remote code execution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MobileCartly 1.0 contains an arbitrary file creation vulnerability in savepage.php where the application directly uses attacker-supplied input in file_put_contents() without any authentication or authorization checks. An unauthenticated attacker can send crafted HTTP GET requests specifying both filename and content parameters, enabling creation of arbitrary files (including PHP scripts) within the pages/ directory or other writable paths, leading to remote code execution.

MitigationImplement authentication and authorization checks before file operations, validate and sanitize filename/content inputs, restrict file creation to whitelisted paths, and remove the savepage.php endpoint from production if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MobileCartly installation and version
    Locate the MobileCartly installation directory and check for version indicators such as a version.php file, footer/copyright notices, or the main index.php page which typically displays the version number
    Affected if The installed version is MobileCartly 1.0 or if the version cannot be determined but matches the product name
  2. Verify savepage.php exists
    Check for the presence of savepage.php in the web root or the scripts directory of the MobileCartly installation
    Affected if savepage.php exists and is accessible via the web server
  3. Inspect savepage.php for vulnerable file_put_contents usage
    Examine the savepage.php source code and look for file_put_contents() or similar file write functions that directly use $_GET parameters for the filename or content arguments without validation
    Affected if The code uses $_GET['filename'] or similar GET parameters directly in file_put_contents() without sanitization or authentication checks
  4. Check web server write permissions
    Verify if the web server process has write permissions to any accessible web directories (such as the cache, pages, or main directory) where arbitrary files could be written
    Affected if The web server user has write access to directories accessible via the web application
  5. Test unauthenticated access to savepage.php
    Attempt to access savepage.php directly via HTTP without any authentication cookies or session tokens
    Affected if The script can be accessed and executed without authentication

The environment is affected if MobileCartly 1.0 is running with savepage.php accessible and the web server has write permissions to web-accessible directories, allowing unauthenticated attackers to create arbitrary files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authentication and authorization checks before file operations, validate and sanitize filename/content inputs, restrict file creation to whitelisted paths, and remove the savepage.php endpoint from production if not required.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-10044 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-10044 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data