LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25976: Piranha CMS - Site-wide Cross-Site Request Forgery (CSRF)

In PiranhaCMS, versions 4.0.0-alpha1 to 9.2.0 are vulnerable to cross-site request forgery (CSRF) when performing various actions supported by the management system, such as deleting a user, deleting a role, editing a post, deleting a media folder etc., when an ID is known.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Piranha CMS had a site-wide CSRF weakness in its management system. If an administrator is tricked into visiting attacker-controlled content while logged in, actions such as deleting users or roles, editing posts, or deleting media folders could be triggered when object IDs are known.

Executive priority

Treat this as high priority for any active PiranhaCMS site with administrative users. The main business risk is unauthorized content or account administration changes, including deletion, after social engineering of a logged-in administrator.

Technical view

CVE-2021-25976 is CWE-352 affecting PiranhaCMS/Piranha versions 4.0.0-alpha1 through 9.2.0. The CVSS 3.1 score is 8.1, reflecting network reachability, low attack complexity, required user interaction, and high integrity and availability impact.

Likely exposure

Organizations are most exposed if they run affected PiranhaCMS versions and administrators access the management interface in normal browser sessions. Risk increases when the management system is reachable from untrusted networks or object IDs are predictable or discoverable.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires user interaction and an authenticated management user’s browser, but the impact can be serious because administrative state-changing actions are in scope.

Researcher notes

The record names broad management actions and requires a known ID, but the bundle does not provide endpoint-level detail. Avoid assuming exploit availability or exact fixed release beyond the referenced upstream commit and affected version range.

Mitigation direction

  • Identify all PiranhaCMS deployments and versions.
  • Prioritize upgrade or remediation for versions 4.0.0-alpha1 through 9.2.0.
  • Review PiranhaCMS vendor guidance and the referenced fix commit.
  • Restrict management access to trusted networks where feasible.
  • Require administrators to use separate sessions for CMS administration.

Validation and detection

  • Confirm deployed PiranhaCMS version is outside the affected range or includes the referenced fix.
  • Review management routes for anti-CSRF protections on state-changing actions.
  • Check whether user, role, post, and media actions require valid CSRF tokens.
  • Verify the management interface is not unnecessarily exposed to the internet.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-25976 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2021-25976Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PiranhaCMSPiranha4.0.0-alpha1, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.