dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-42176

MEDIUM · 6.7 CVSS v3.1 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Scoold versions before 1.67.0 contain an authentication bypass where a forged Bearer token is accepted as a valid admin API token on the /api/config/set/admins endpoint. Attackers can modify the scoold.admins configuration value to add their email address, which takes effect after application restart, providing persistent admin access.

MitigationUpgrade to Scoold version 1.67.0 or later. Until patched, restrict network access to /api/config/set/* endpoints and monitor configuration files for unauthorized modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Scoold version
    Locate the version by checking the JAR file name, pom.xml in the source directory, or the version line in application startup logs. Look for files like scoold-x.x.x.jar or examine build artifacts.
    Affected if The installed version is before 1.67.0 (for example, 1.66.0, 1.65.3, etc.)
  2. Inspect the scoold.admins configuration value
    Open the main configuration file (typically application.conf or scoold.conf) and locate the scoold.admins or parode.admins setting. This is usually a comma-separated list of email addresses authorized as administrators.
    Affected if The configuration contains email addresses that were not intentionally added by your legitimate admin team, or contains unexpected entries.
  3. Review application logs for configuration change attempts
    Search application log files for requests to the /api/config/set/admins endpoint. Look for POST or PUT requests to this path, especially those that may have succeeded.
    Affected if Logs show any requests to /api/config/set/admins that were not initiated by your own administrators, or show successful configuration modifications.

You are affected if Scoold version is below 1.67.0 AND the scoold.admins configuration contains unexpected email addresses or logs show unauthorized attempts to modify admin settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Scoold version 1.67.0 or later. Until patched, restrict network access to /api/config/set/* endpoints and monitor configuration files for unauthorized modifications.

Recommended fix High confidence

1.67.0

  1. Upgrade Scoold to version 1.67.0 or later
  2. After upgrading, verify the /api/config/set/admins endpoint now requires proper authentication
  3. Review the scoold.admins configuration to ensure no unauthorized admin accounts were added
  4. If compromise is suspected, audit configuration files for any unauthorized entries
  5. Restart the Scoold service to load the patched configuration

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42176 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42176 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data