/

CVE-2026-30707

Severity:

HIGH RISK

(8.1)

Broken Access Control in SpeedExam ReviewAnswerDetails API

CVE-2026-30707

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Exposure of Exam Answer Keys and Assessment Integrity Compromise

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

SpeedExam Online Examination System (SaaS) after v.FEV2026 contains a broken access control issue in the ReviewAnswerDetails ASP.NET PageMethod, which exposes full exam answer keys to unauthorized callers.

Authenticated users can bypass client-side restrictions and directly invoke this backend method, enabling retrieval of the full answer key for assessments they should not be able to review.

Affected context

The vulnerability occurs in SpeedExam Online Examination System deployments that expose the ReviewAnswerDetails ASP.NET PageMethod as part of the web application.

It manifests when server-side authorization checks are missing or incomplete, and the backend API trusts the client UI to enforce who may review answer details.

Any environment where users can access the application's JavaScript or network traffic (e.g., browser dev tools) and see or reconstruct the PageMethod call may be affected.

Exploit preconditions

  • Attack surface: HTTP(S) endpoint hosting the ReviewAnswerDetails ASP.NET PageMethod
  • Required access: Any authenticated account with the ability to reach the application (e.g., student/test-taker login)
  • Trigger point: Direct invocation of the ReviewAnswerDetails backend method via crafted HTTP requests, independent of the normal UI
  • Why exploitation is possible: Authorization is enforced primarily on the client side (or not enforced at all), and the server-side method does not robustly verify that the requesting user is authorized to view the requested exam's answer details

Why this happens

This issue stems from relying on client-side controls (such as hidden buttons, disabled UI elements, or JavaScript checks) to restrict access to sensitive functionality instead of enforcing authorization on the server.

The ReviewAnswerDetails PageMethod accepts parameters from the client and returns full answer details without sufficiently verifying that the caller is permitted to access that exam's answer key.

Conceptually, this maps to CWE-284: Improper Access Control, where the system fails to enforce appropriate authorization checks on sensitive operations or data, allowing authenticated but unauthorized users to perform actions beyond their intended privileges.

Potential impact

  • Unauthorized retrieval of full answer keys for active or future exams
  • Compromise of exam integrity and fairness across cohorts or test sessions
  • Facilitation of large-scale cheating and sharing of answer banks
  • Damage to the reputation of the examination provider or institution
  • Potential regulatory or contractual non-compliance where exam integrity is mandated

General mitigation guidance

Effective mitigation focuses on enforcing server-side authorization and minimizing reliance on client-side controls:

  • Implement robust server-side checks in the ReviewAnswerDetails method to verify that the authenticated user is explicitly authorized to access answer details for a given exam, candidate, and time window.
  • Use a clear authorization model (e.g., role- and context-based access control) so that only appropriate roles (e.g., exam admins, proctors) can retrieve answer keys.
  • Treat all client-supplied identifiers (exam IDs, user IDs, attempt IDs) as untrusted; derive authorization context on the server using the authenticated session, not client parameters.
  • Limit when answer keys are ever exposed (e.g., only for finalized attempts, only in post-exam review windows, and only as aggregated feedback instead of raw keys where possible).
  • Apply the principle of least privilege to API endpoints and isolate sensitive review/answer functionality into hardened services or routes.

How teams detect issues like this

Organizations can detect and monitor for similar access control weaknesses by:

  • Reviewing backend controller/PageMethod code for sensitive operations that lack explicit server-side authorization checks.
  • Using static analysis or linting rules that flag public web methods or APIs returning sensitive exam/answer data without role or permission verification.
  • Implementing API gateway or middleware policies requiring authorization attributes/filters on all data-retrieval endpoints involving assessment content.
  • Monitoring logs for unusual patterns, such as a single account accessing many different candidates' exam details or repeated direct calls to review endpoints outside normal UI flows.
  • Conducting targeted penetration tests and security reviews that focus on bypassing client-side logic and invoking JSON/PageMethod endpoints directly.

Sources

SourceLink
github.comgithub.com/Maarckz/VulnReports/blob/main/CVE-2026-30707.md
github.comgithub.com/Maarckz/VulnReports/blob/main/SpeedExam%20%28SECOPS.GROUP%29.md

Frequently asked

questions

Yes. Any remote user with valid credentials and network access to the application can potentially exploit the issue by calling the vulnerable PageMethod directly.

No. The issue can typically be triggered by standard authenticated users (such as regular test-takers) if server-side authorization is missing or insufficient.

Enforce strict server-side authorization checks in the ReviewAnswerDetails method, ensuring that the operation is only available to properly authorized roles and only within appropriate exam contexts, independent of any client-side logic.

Design APIs under a "never trust the client" model, require authorization on every sensitive endpoint, use centralized authorization middleware or attributes, and routinely test APIs by bypassing the UI and calling methods directly as part of security review and CI pipelines.

Find out what's already
exploitable in your codebase.