CVE-2009-3814: Code Injection
First published: Tue Oct 27 2009(Updated: )
Static code injection vulnerability in RunCMS 2M1 allows remote authenticated administrators to execute arbitrary PHP code via the "Filter/Banning" feature, as demonstrated by modifying modules/system/cache/bademails.php using the "Prohibited: Emails" action, and other unspecified filters.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Runcms | =2m1 |
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-2009-3814?
CVE-2009-3814 is classified as a high severity vulnerability due to its potential for remote code execution.
How do I fix CVE-2009-3814?
To mitigate CVE-2009-3814, you should update RunCMS to a version where this vulnerability is patched.
Who is affected by CVE-2009-3814?
CVE-2009-3814 affects remote authenticated administrators using RunCMS version 2M1.
What kind of attack can exploit CVE-2009-3814?
CVE-2009-3814 can be exploited to execute arbitrary PHP code through the Filter/Banning feature.
What is the cause of CVE-2009-3814?
The cause of CVE-2009-3814 is a static code injection vulnerability in the RunCMS application.
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/last-modified-date
- agent/severity
- agent/author
- agent/description
- agent/event
- agent/source
- agent/tags
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/weakness
- vendor/runcms
- canonical/runcms
- version/runcms/2m1