CVE-2005-1031
First published: Sat Apr 09 2005(Updated: )
RUNCMS 1.1A, and possibly other products based on e-Xoops (exoops), when "Allow custom avatar upload" is enabled, does not properly verify uploaded files, which allows remote attackers to upload arbitrary files.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Xoops Xm Memberstats | =1.05r3 | |
| Runcms | =1.1 | |
| Runcms | =1.1a |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2005-1031?
CVE-2005-1031 is classified as a critical vulnerability due to its potential for remote code execution.
How do I fix CVE-2005-1031?
To mitigate CVE-2005-1031, disable the 'Allow custom avatar upload' feature in your RUNCMS or e-Xoops installation.
Which versions are affected by CVE-2005-1031?
CVE-2005-1031 affects RUNCMS versions 1.1 and 1.1A, and possibly other products based on e-Xoops.
What kind of attack does CVE-2005-1031 enable?
CVE-2005-1031 allows remote attackers to upload arbitrary files, potentially leading to remote code execution.
Is there a patch available for CVE-2005-1031?
As of now, there is no specific patch for CVE-2005-1031, and the recommended action is to adjust settings to restrict file uploads.
- agent/type
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/references
- agent/last-modified-date
- agent/severity
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/e-xoops
- canonical/xoops xm memberstats
- version/xoops xm memberstats/1.05r3
- vendor/runcms
- canonical/runcms
- version/runcms/1.1
- version/runcms/1.1a