LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27632: Talishar Vulnerable to Cross-Site Request Forgery (CSRF)

Talishar is a fan-made Flesh and Blood project. Prior to commit 6be3871a14c192d1fb8146cdbc76f29f27c1cf48, the Talishar application lacks Cross-Site Request Forgery (CSRF) protections on critical state-changing endpoints, specifically within `SubmitChat.php` and other game interaction handlers. By failing to require unique, unpredictable session tokens, the application allows third-party malicious websites to forge requests on behalf of authenticated users, leading to unauthorized actions within active game sessions. The attacker would need to know both the proper gameName and playerID for the player. The player would also need to be browsing and interact with the infected website while playing a game. The vulnerability is fixed in commit 6be3871a14c192d1fb8146cdbc76f29f27c1cf48.

LowCVSS 2.6Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2026-27632 affects Talishar, a fan-made Flesh and Blood project. Older versions lack CSRF protections on chat and game action endpoints. A malicious site could cause an authenticated player to perform unintended in-game actions, but only under specific conditions. The published severity is low.

Executive priority

Treat as a low-priority fix unless Talishar is publicly hosted or heavily used. Apply the fixed commit during normal maintenance, because the impact is limited but user trust and game integrity can be affected.

Technical view

Before commit 6be3871a14c192d1fb8146cdbc76f29f27c1cf48, Talishar did not require unique, unpredictable CSRF tokens on critical state-changing endpoints, including SubmitChat.php and other game interaction handlers. Exploitation requires user interaction, an authenticated active game session, and attacker knowledge of gameName and playerID. CWE-352 applies. CVSS v3.1 is 2.6.

Likely exposure

Exposure appears limited to Talishar deployments running code before commit 6be3871a14c192d1fb8146cdbc76f29f27c1cf48. The issue is relevant when users play while authenticated and can be induced to interact with a malicious website.

Exploitation context

No provided source states active exploitation, and it is not listed as KEV. Practical exploitation requires multiple conditions: authenticated player, active session, user interaction with a malicious site, and attacker knowledge of the gameName and playerID.

Researcher notes

Evidence is limited to the CVE record and GitHub advisory metadata in the provided bundle. The advisory identifies the fixed commit and affected endpoint class but does not provide broader exploit telemetry. Avoid assuming impact outside Talishar or versions before the named commit.

Mitigation direction

  • Update Talishar to commit 6be3871a14c192d1fb8146cdbc76f29f27c1cf48 or later.
  • Review the GitHub advisory for any additional vendor guidance.
  • Ensure state-changing game and chat endpoints require unpredictable CSRF tokens.

Validation and detection

  • Identify the deployed Talishar commit or release version.
  • Confirm it is at or after commit 6be3871a14c192d1fb8146cdbc76f29f27c1cf48.
  • Verify SubmitChat.php and game handlers enforce CSRF token checks.
  • Confirm unauthorized cross-site requests cannot change game state.
Prepared
Confidence
high
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-2026-27632 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
Low
CVSS
2.6 (3.1)
Known Exploited
No
Published

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

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
2.6CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N1.21.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.6Low
CVSS 3.1 vector shape for CVE-2026-27632Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
TalisharTalishar< 6be3871a14c192d1fb8146cdbc76f29f27c1cf48Listed
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.