CVE-2009-4787: CSRF

Published Apr 21, 2010
·
Updated

Multiple cross-site request forgery (CSRF) vulnerabilities in Pligg before 1.0.3 allow remote attackers to hijack the authentication of administrators for requests that create user accounts or have unspecified other impact.

Affected Software

8 affected components
Pligg Pligg CMS<=1.0.2
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.0-rc1
Pligg Pligg CMS=1.0.0-rc5
Pligg Pligg CMS=1.0.0-rc4

Event History

Apr 21, 2010
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·02:30 PM
DescriptionSeverityWeaknessAffected Software
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-2009-4787?

CVE-2009-4787 has been classified as a medium severity vulnerability.

2

How do I fix CVE-2009-4787?

To fix CVE-2009-4787, upgrade to Pligg CMS version 1.0.3 or later.

3

What types of attacks does CVE-2009-4787 allow?

CVE-2009-4787 allows remote attackers to hijack the authentication of administrators through cross-site request forgery.

4

Which versions of Pligg CMS are affected by CVE-2009-4787?

CVE-2009-4787 affects Pligg CMS versions before 1.0.3, including version 1.0.0-rc3 and earlier.

5

Who is at risk from CVE-2009-4787?

Administrators using affected versions of Pligg CMS are at risk from CVE-2009-4787.

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