Skip to main content
VulnerabilityPublished

CVE-2026-53760: Admidio · CSRF on Plugin Install, Uninstall, and Update via Unprotected GET Requests

Affects admidio/admidioSource GCVE Database

0
Compare

Not known to be exploited · CVSS 5.2 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
5.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Packagistadmidio/admidioAffected
  • <=5.0.11
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The recommended fix is to change plugin management operations from GET to POST requests and add CSRF token validation using SecurityUtils::validateCsrfToken() consistent with other administrative operations. Until a patch is available, administrators should avoid visiting untrusted web pages while authenticated and consider restricting access to the plugin management interface. Monitor vendor channels for official updates or patches.

Description

Admidio versions up to 5.0.11 have a CSRF vulnerability in the modules/plugins.php endpoint, which handles plugin install, uninstall, and update operations via GET requests without CSRF token validation. An attacker can trick an authenticated administrator into visiting a malicious page that triggers these operations, including uninstalling plugins. The uninstall operation executes SQL scripts that drop database tables, causing irreversible data loss. The vulnerability arises because these state-changing operations lack CSRF protection and rely on GET requests, which browsers send with session cookies under SameSite=Lax. The recommended fix is to switch these operations to POST requests and add CSRF token validation.

References

Community reviews

Loading reviews…