CVE-2010-1514
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 · uneditedUnrestricted file upload vulnerability in TomatoCMS 2.0.6 and earlier allows remote authenticated users, with certain privileges, to execute arbitrary PHP code by uploading an image file, and then accessing it via a direct request to the file in an unspecified directory.
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 confidenceTomatoCMS 2.0.6 and earlier contains an unrestricted file upload vulnerability allowing authenticated users with specific privileges to upload files with image extensions (e.g., .jpg, .png) that contain embedded PHP code. The application stores these files in a web-accessible directory without proper validation, enabling remote code execution when the file is accessed directly via HTTP.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.0.6= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.3.1430= 2.0.3.1622= 2.0.4= 2.0.5CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm TomatoCMS installation and versionLocate TomatoCMS in your webroot and check the version file or dashboard. Common locations include a version.php, about page, or installer directory. Compare your version against the affected range: 2.0.0 through 2.0.6 (including 2.0.3.1430 and 2.0.3.1622).Affected if Installed version is 2.0.6 or any version listed in the affected products (2.0.0 through 2.0.5, including specific builds 2.0.3.1430 and 2.0.3.1622).
-
Identify if file upload module is enabledLog in as an authenticated user with upload privileges. Navigate to the file/media upload functionality. Common paths include /admin/core/media/upload or /admin/media/attachment. Check if the upload form accepts image extensions (.jpg, .png, .gif).Affected if The file upload feature is accessible and accepts files with image extensions without additional content-type validation.
-
Locate uploaded files in web-accessible directoriesSearch the webroot for directories containing uploaded media. Common locations: /uploads/, /media/, /files/, /attached/. List all files in these directories, particularly looking for files with image extensions (.jpg, .png) that may contain PHP code.Affected if Uploaded files are stored in directories directly accessible via HTTP (web-accessible paths).
-
Test uploaded file for PHP execution capabilityIf you can upload a test file, create a file with a .jpg extension containing PHP code (e.g., <?php phpinfo(); ?>) and upload it. Then access the file directly via browser using its URL to see if the PHP code executes.Affected if The uploaded file with an image extension is served by the web server and the embedded PHP code executes when the file is accessed via HTTP.
You are affected if TomatoCMS version 2.0.6 or earlier is installed, the file upload module is enabled for authenticated users, and uploaded files with image extensions are stored in web-accessible directories where they can be executed as PHP code.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict server-side validation of uploaded files (verifying actual file content/MIME type, not just extension), store uploaded files outside the webroot or disable script execution via web server configuration, and restrict file upload privileges to minimal necessary roles.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1514 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-1514 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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