Coyote-OSS Coyote Wiki /Comment/Save save improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00+ |
Summary
A vulnerability, which was classified as problematic, has been found in Coyote-OSS Coyote. Affected by this vulnerability is the function Wiki\CommentController::save of the file /Comment/Save of the component Wiki. This manipulation causes improper authorization.
The identification of this vulnerability is CVE-2026-130864. It is possible to initiate the attack remotely. There is no exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as problematic was found in Coyote-OSS Coyote (affected version unknown). Affected by this vulnerability is the function Wiki\CommentController::save of the file /Comment/Save of the component Wiki. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect integrity. The summary by CVE is:
Coyote before commit d6e8fb9 contains a missing authorization vulnerability in Wiki\CommentController::save that allows authenticated users to edit other users' wiki comments. Attackers can send POST requests to /Comment/Save/{wiki}/{id} with another user's comment id, bypassing the WikiCommentPolicy update check, so altered text appears under the original author's name.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-130864 since 11/17/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
Applying the patch d6e8fb9f7a584b841101cf58ba1096a5eba85dc0 is able to eliminate this problem.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: d6e8fb9f7a584b841101cf58ba1096a5eba85dc0
Timeline
11/17/2026 Advisory disclosed11/17/2026 CVE reserved
11/17/2026 VulDB entry created
11/17/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CNA: VulnCheck
CVE: CVE-2026-130864 (🔒)
GCVE (CVE): GCVE-0-2026-130864
GCVE (VulDB): GCVE-100-438229
Entry
Created: 11/17/2026 21:16Changes: 11/17/2026 21:16 (77)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.