What is the severity of CVE-2009-2269?

CVE-2009-2269 is classified as a critical vulnerability due to the potential for remote attackers to execute arbitrary SQL commands.

How do I fix CVE-2009-2269?

Fixing CVE-2009-2269 requires upgrading to a patched version of Empire CMS that addresses this SQL injection vulnerability.

Can CVE-2009-2269 be exploited remotely?

Yes, CVE-2009-2269 can be exploited remotely by attackers targeting the bid parameter.

Which versions of Empire CMS are affected by CVE-2009-2269?

CVE-2009-2269 specifically affects version 5.1 of Empire CMS.

What types of attacks can CVE-2009-2269 facilitate?

CVE-2009-2269 can facilitate SQL injection attacks that may allow unauthorized access to the database and data manipulation.

Vulnerability/
CVE-2009-2269

high

7.5

CWE

1/7/2009

7/8/2024

CVE-2009-2269: SQL Injection

First published: Wed Jul 01 2009(Updated: )

SQL injection vulnerability in Empire CMS 5.1 allows remote attackers to execute arbitrary SQL commands via the bid parameter to the default URI under e/tool/gbook/.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Phome Empire	=5.1

Never miss a vulnerability like this again

Reference Links

http://www.securityfocus.com/archive/1/504652/100/0/threaded

Frequently Asked Questions

What is the severity of CVE-2009-2269?
CVE-2009-2269 is classified as a critical vulnerability due to the potential for remote attackers to execute arbitrary SQL commands.
How do I fix CVE-2009-2269?
Fixing CVE-2009-2269 requires upgrading to a patched version of Empire CMS that addresses this SQL injection vulnerability.
Can CVE-2009-2269 be exploited remotely?
Yes, CVE-2009-2269 can be exploited remotely by attackers targeting the bid parameter.
Which versions of Empire CMS are affected by CVE-2009-2269?
CVE-2009-2269 specifically affects version 5.1 of Empire CMS.
What types of attacks can CVE-2009-2269 facilitate?
CVE-2009-2269 can facilitate SQL injection attacks that may allow unauthorized access to the database and data manipulation.

agent/softwarecombine
agent/type
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/references
agent/severity
agent/weakness
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/phome empire
canonical/phome empire
version/phome empire/5.1

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-2269?
CVE-2009-2269 is classified as a critical vulnerability due to the potential for remote attackers to execute arbitrary SQL commands.
How do I fix CVE-2009-2269?
Fixing CVE-2009-2269 requires upgrading to a patched version of Empire CMS that addresses this SQL injection vulnerability.
Can CVE-2009-2269 be exploited remotely?
Yes, CVE-2009-2269 can be exploited remotely by attackers targeting the bid parameter.
Which versions of Empire CMS are affected by CVE-2009-2269?
CVE-2009-2269 specifically affects version 5.1 of Empire CMS.
What types of attacks can CVE-2009-2269 facilitate?
CVE-2009-2269 can facilitate SQL injection attacks that may allow unauthorized access to the database and data manipulation.