Skip to main content

Scoold EUVDEUVD-2026-18529

| CVE-2026-34832 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-04-02 GitHub_M
6.5
CVSS 3.1 · Vendor: GitHub_M
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Impact

This vulnerability presents moderate real-world risk despite the CVSS score of 6.5. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) indicates network-accessible exploitation with low complexity and no user interaction, making it trivially exploitable by any authenticated user. The impact is limited to integrity (unauthorized deletion), not confidentiality or availability, which constrains the blast radius. However, the authentication requirement (PR:L) is significant: attackers must first obtain valid credentials, likely through phishing, credential stuffing, or as an insider threat. In a team collaboration setting, this is a material risk because legitimate employees can be damaged by malicious colleagues deleting their contributions without recovery. SSVC would classify this as exploitable with high technical impact but mitigated by authentication requirements. The lack of any public exploit, KEV status, or known active exploitation suggests this is a defensive discovery rather than an urgent zero-day, making prioritization below critical but above informational.

Exploit ScenarioDerived

A disgruntled team member with valid Scoold credentials discovers the endpoint and uses a browser developer console or curl command to POST to /feedback/{id}/delete with a victim's feedback ID obtained from the public feedback listing. The request succeeds without authentication challenge because the user is already logged in, and the server does not check ownership; the victim's feedback disappears immediately from the platform, with no audit trail or recovery option. This scenario requires only network access and valid credentials, not administrator privileges, making it practical for any team member.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 02, 2026

Scoold versions prior to 1.66.1 allow authenticated low-privilege users to delete any other user's feedback posts via an authorization flaw in the POST /feedback/{id}/delete endpoint. The vulnerability requires login but lacks object ownership verification, enabling lateral privilege escalation where any team member can destroy feedback created by colleagues or administrators. No public exploit code or active exploitation has been identified; the issue was discovered during code review and patched in version 1.66.1.

RemediationAI

Vendor-released patch: Upgrade Scoold to version 1.66.1 or later. The fix is available directly from the GitHub releases page (https://github.com/Erudika/scoold/releases/tag/1.66.1) and the security advisory (https://github.com/Erudika/scoold/security/advisories/GHSA-g5fv-xw88-vw44). The upstream commit 5def88c25405cc60482292bcceb45dc024e899fe implements authorization checks to verify object ownership before allowing deletion. If immediate upgrade is not feasible, restrict feedback deletion capabilities to administrators only through role-based access control settings, or temporarily disable feedback deletion for non-admin users by adjusting application permissions until patched.

Affected VersionsENISA

scoold < 1.66.1

Affected Packages

euvd scoold fix: 1.66.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Scoold is a Java-based Q&A and knowledge-sharing platform built on the Erudika framework. The vulnerability exists in the feedback deletion handler, which properly enforces authentication (requiring PR:L privilege level per CVSS vector) but fails to implement authorization checks for resource ownership. The flaw is classified as CWE-639 (Authorization Bypass Through User-Controlled Key), a common pattern in REST APIs where user IDs or resource IDs are trusted without validating that the requesting user owns or has permission to modify the target resource. The endpoint accepts POST requests with a feedback ID parameter and immediately processes deletion without comparing the authenticated user's identity against the feedback's creator or checking for moderator/admin status.

Know when Scoold gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Primary rating from Vendor (GitHub_M) · only source for this CVE.

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

2
Patch available
Apr 16, 2026 - 05:29 EUVD
1.66.1
CVE Published
Apr 02, 2026 - 19:08 nvd
MEDIUM 6.5

DescriptionCVE.org

Scoold is a Q&A and a knowledge sharing platform for teams. Prior to version 1.66.1, Scoold contains an authenticated authorization flaw in feedback deletion that allows any logged-in, low-privilege user to delete another user's feedback post by submitting its ID to POST /feedback/{id}/delete. The handler enforces authentication but does not enforce object ownership (or moderator/admin authorization) before deletion. In verification, a second non-privileged account successfully deleted a victim account's feedback item, and the item immediately disappeared from the feedback listing/detail views. This issue has been patched in version 1.66.1.

Threat Intelligence Overview

EPSS Score
0.0%
Top 86% exploitable
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy