CVE-2010-2577: SQL Injection

Published Aug 16, 2010
·
Updated

Multiple SQL injection vulnerabilities in Pligg before 1.1.1 allow remote attackers to execute arbitrary SQL commands via the title parameter to (1) storyrss.php or (2) story.php.

Affected Software

11 affected components
Pligg Pligg CMS<=1.1.0
Pligg Pligg CMS=1.0.0-rc3
Pligg Pligg CMS=1.0.1
Pligg Pligg CMS=1.0.0-rc2
Pligg Pligg CMS=1.0.0
Pligg Pligg CMS=1.0.4
Pligg Pligg CMS=1.0.2
Pligg Pligg CMS=1.0.0-rc1
Pligg Pligg CMS=1.0.0-rc5
Pligg Pligg CMS=1.0.0-rc4
Pligg Pligg CMS=1.0.3

Event History

Aug 16, 2010
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2010-2577?

CVE-2010-2577 is classified as a high-severity vulnerability due to its ability to allow remote attackers to execute arbitrary SQL commands.

2

How do I fix CVE-2010-2577?

To fix CVE-2010-2577, upgrade Pligg CMS to version 1.1.1 or later.

3

What versions of Pligg CMS are affected by CVE-2010-2577?

Versions of Pligg CMS prior to 1.1.1, including 1.0.0 through 1.0.4 and release candidates, are vulnerable to CVE-2010-2577.

4

What types of attacks can CVE-2010-2577 enable?

CVE-2010-2577 can enable SQL injection attacks that may lead to unauthorized database access and manipulation.

5

Is CVE-2010-2577 a waste of time to address?

Addressing CVE-2010-2577 is essential as failing to do so can result in serious data breaches and security incidents.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203