CVE-2026-54676 Erudika CVE debrief

Who should care

Defenders responsible for Scoold deployments, administrators, and users with personal API tokens should assess exposure and apply the fix to prevent unauthorized access to private discussions.

Why it matters

CVE-2026-54676 allows unauthorized access to private discussions in Scoold Q&A platform prior to version 1.69.0. Defenders should verify exposure, restrict API token access, and apply the fix to prevent data leakage.

• Potential unauthorized access to confidential team or project discussions.
• Exposure of private reply bodies through the answers endpoint.
• Verification priority for Scoold deployments and user API token management.
• Potential data leakage through API token exploitation.

Technical summary

The vulnerability is caused by the lack of access control in the ApiController.getPostReplies() method, which allows users with personal API tokens to retrieve replies from questions in private spaces they cannot access. This issue is reachable when scoold.api_user_access_enabled and scoold.api_enabled are true and a token holder knows or enumerates a private question identifier. The vulnerability allows unauthorized access to private discussions, potentially exposing confidential team or project information. To mitigate this issue, defenders should verify exposure, restrict API token access, and apply the fix by upgrading to Scoold version 1.69.0 or later.

Defensive priority

Defenders should prioritize verifying exposure and applying the fix, as the vulnerability allows unauthorized access to private discussions.

Recommended defensive actions

• Verify if Scoold is deployed and if users have personal API tokens enabled.
• Check if the scoold.api_user_access_enabled and scoold.api_enabled configurations are true.
• Apply the fix by upgrading to Scoold version 1.69.0 or later.
• Review and restrict API token access and permissions.
• Confirm whether affected Scoold deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The vulnerability is confirmed in Scoold versions prior to 1.69.0. The issue is reachable when scoold.api_user_access_enabled and scoold.api_enabled are true and a token holder knows or enumerates a private question identifier.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.