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.

Vulnerability/
CVE-2009-3814

medium

6.5

CWE

27/10/2009

3/10/2022

7/8/2024

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 Runcms	=2m1

Never miss a vulnerability like this again

Reference Links

http://retrogod.altervista.org/9sg_runcms_forum_sql.html

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.

collector/nvd-historical
collector/nvd-index
agent/type
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/references
agent/last-modified-date
agent/severity
agent/author
agent/description
agent/tags
agent/event
agent/source
vendor/runcms
canonical/runcms runcms
version/runcms runcms/2m1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

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.