CVE-2024-42611: Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) via admin/admin_page.php?link_i

This month

HIGH 8.8DOWNGRADE

CVE-2024-42611 is a high-severity flaw (CVSS 8.8) affecting pligg cms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) via admin/admin_page.php?link_id=1&mode=delete

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 78%)
CISA exploited list	No
Weakness	CWE-352
Published	2024-08-20
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: pligg

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-08-20 15:15 UTCPublished CVE record published
2026-06-17 07:49 UTCUpdated Record last modified

pligg pligg cms DOWNGRADE

Affected: 2.0.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.2

1. Check installed version

apt-cache policy pligg-cms || rpm -q pligg-cms || pligg-cms --version

2. No fixed release: DOWNGRADE to a release before 2.0.2 (Debian / Ubuntu)

apt-cache madison pligg-cms sudo apt install pligg-cms=<VERSION_BEFORE_2.0.2> sudo apt-mark hold pligg-cms

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list pligg-cms sudo dnf downgrade pligg-cms-<VERSION_BEFORE_2.0.2> sudo dnf versionlock add pligg-cms

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-42611?

pligg cms: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-42611 being exploited?

CVE-2024-42611 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-42611 affect?

CVE-2024-42611 affects pligg cms. Severity is high (CVSS 8.8). Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) via admin/admin_page.php?link_id=1&mode=delete

How urgent is CVE-2024-42611?

Priority 41/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2024-42621 HIGH 8.8 DOWNGRADE Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/admin_
CVE-2024-42619 HIGH 8.8 DOWNGRADE Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/domain
CVE-2024-42618 HIGH 8.8 DOWNGRADE Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /module.php?m
CVE-2024-42617 HIGH 8.8 DOWNGRADE Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/admin_
CVE-2024-42616 HIGH 8.8 DOWNGRADE Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/admin_

References

← Back to latest CVEs