CVE-2026-42176
Received Received - Intake
Authentication Bypass in Scoold via Forged Bearer Token

Publication date: 2026-05-08

Last updated on: 2026-05-08

Assigner: GitHub, Inc.

Description
Scoold is a Q&A and a knowledge sharing platform for teams. Prior to version 1.67.0, Scoold allows the admins configuration value to be modified through /api/config/set/admins with a forged Bearer token that is accepted as an admin API token. Once that setting is changed, the target email address is written to the application configuration file. The change does not become active immediately in the current process, because the ADMINS set is loaded once at startup. After a Scoold restart, though, the selected user is recognized as an administrator and gains access to the admin panel. This issue gives an attacker a reliable persistence path: write their own email into scoold.admins, wait for a restart or trigger one operationally, and the account comes back as admin. This issue has been patched in version 1.67.0.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-08
Last Modified
2026-05-08
Generated
2026-05-09
AI Q&A
2026-05-08
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
scoold scoold to 1.67.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability affects Scoold, a Q&A and knowledge sharing platform for teams, in versions prior to 1.67.0. It allows an attacker to modify the admins configuration value by sending a request to the /api/config/set/admins endpoint with a forged Bearer token that is accepted as an admin API token.

When the attacker changes this setting, their chosen email address is written into the application configuration file. Although the change does not take effect immediately because the admin list is loaded only at startup, after the application restarts, the attacker’s account is recognized as an administrator and gains access to the admin panel.

This provides the attacker with a reliable persistence mechanism to regain admin access by writing their email into the admin list and triggering or waiting for a restart.


How can this vulnerability impact me? :

This vulnerability can have serious impacts because it allows an attacker to gain persistent administrative access to the Scoold platform.

  • The attacker can modify critical configurations and access sensitive data through the admin panel.
  • They can maintain their admin privileges even after restarts, making it difficult to remove their access.
  • This could lead to unauthorized data exposure, data manipulation, or disruption of service.

What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, you should upgrade Scoold to version 1.67.0 or later, where the issue has been patched.

Additionally, if you suspect that the configuration has been tampered with, review and reset the admins configuration value in the application configuration file.

Restart the Scoold application after making these changes to ensure that the updated configuration is loaded and unauthorized admin accounts are removed.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability allows an attacker to gain persistent administrative access to the Scoold platform by modifying the admin configuration through a forged token. Such unauthorized access can lead to exposure or modification of sensitive data, which may violate data protection requirements under regulations like GDPR and HIPAA.

Specifically, the high impact on confidentiality and integrity indicated by the CVSS score suggests that personal or protected health information could be compromised or altered without authorization, undermining compliance with these standards.

Furthermore, the persistence of the attack after service restarts increases the risk of prolonged unauthorized access, complicating incident response and breach notification obligations under these regulations.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves unauthorized modification of the admin configuration via a forged Bearer token sent to the /api/config/set/admins endpoint.

To detect this vulnerability on your network or system, you can monitor for suspicious HTTP requests targeting the /api/config/set/admins endpoint, especially those containing Bearer tokens that may be forged.

Commands to help detect such activity could include network traffic inspection or web server access log analysis. For example:

  • Using grep to search web server logs for requests to the vulnerable endpoint: grep "/api/config/set/admins" /var/log/nginx/access.log
  • Using tcpdump or tshark to capture and filter HTTP traffic for suspicious Bearer tokens: sudo tcpdump -A -s 0 'tcp port 80 or tcp port 443' | grep 'Authorization: Bearer'
  • Checking the application configuration file for unexpected changes to the scoold.admins setting, which may indicate exploitation.

Note that detection requires monitoring for unauthorized access attempts with high privileges, as the attack requires network access and elevated permissions.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart