LiveActive security incident?Get immediate response
CVE Record

CVE-2021-34167: Cross Site Request Forgery (CSRF) vulnerability in taoCMS 3.0.2 allows remote attackers to gain escalated p...

Cross Site Request Forgery (CSRF) vulnerability in taoCMS 3.0.2 allows remote attackers to gain escalated privileges via taocms/admin/admin.php.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

taoCMS 3.0.2 has a CSRF flaw affecting its admin area. If an administrator is tricked into interacting with attacker-controlled content, privileged changes may be made through the administrator’s browser. The CVE rates this high severity, but the supplied sources do not confirm active exploitation or a vendor patch.

Executive priority

Prioritize this where taoCMS 3.0.2 supports public or business-critical services. The main business risk is unauthorized administrative change through a targeted administrator, with potentially high data and service impact.

Technical view

CVE-2021-34167 is a CWE-352 CSRF issue in taoCMS 3.0.2 via taocms/admin/admin.php. CVSS 3.1 is 8.8 with network attack vector, low complexity, no attacker privileges, required user interaction, and high confidentiality, integrity, and availability impact. Product metadata is incomplete in the CVE record.

Likely exposure

Exposure is limited to organizations running taoCMS 3.0.2, especially where administrative interfaces are reachable by administrators during normal browsing. The provided record lists affected vendor and product as n/a, so asset confirmation is required.

Exploitation context

The CVE is not listed as CISA KEV in the supplied bundle. The sources describe a CSRF privilege-escalation risk requiring user interaction, but they do not provide evidence of exploitation in the wild.

Researcher notes

The CVE record provides a high CVSS score and a single GitHub issue reference, but affected CPE data is absent. Avoid broad product assumptions beyond taoCMS 3.0.2 and validate remediation status from upstream sources.

Mitigation direction

  • Check taoCMS project guidance and the referenced issue for an official fix or workaround.
  • Restrict taoCMS admin access to trusted networks, VPN, or administrative jump hosts.
  • Upgrade, replace, or retire taoCMS 3.0.2 if vendor-supported remediation is available.
  • Review admin workflows for CSRF protections before relying on compensating controls.
  • Increase monitoring for unexpected account, role, or configuration changes.

Validation and detection

  • Inventory public and internal taoCMS deployments and confirm exact versions.
  • Identify whether taocms/admin/admin.php is reachable from untrusted networks.
  • Review administrative forms for anti-CSRF tokens and safe request handling.
  • Check audit logs for unexpected privilege, account, or configuration changes.
  • Document whether vendor remediation exists before closing the finding.
Prepared
Confidence
medium
Sources
3

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-34167 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.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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
2Source 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.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
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.