dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-30707

HIGH · 8.1 CVSS v3.1 Published 2026-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
An issue was discovered in SpeedExam Online Examination System (SaaS) after v.FEV2026. It allows Broken Access Control via the ReviewAnswerDetails ASP.NET PageMethod. Authenticated attackers can bypass client-side restrictions and invoke this method directly to retrieve the full answer key. The provider states that this issue is "Fixed in [02/2026] backend service update."

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

SpeedExam Online Examination System contains a Broken Access Control vulnerability in the ReviewAnswerDetails ASP.NET PageMethod. Authenticated attackers can bypass client-side restrictions and directly invoke this method to retrieve answer keys they should not have access to, indicating missing server-side authorization checks.

MitigationApply the vendor's February 2026 backend service update to remediate this vulnerability. Until then, implement server-side authorization validation on the PageMethod and monitor for unauthorized answer key access.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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. Confirm SpeedExam installation
    Identify if SpeedExam Online Examination System is present in your environment. Check web server configurations, application directories, or running services for SpeedExam components.
    Affected if SpeedExam Online Examination System is deployed
  2. Identify installed version
    Locate version information for the SpeedExam installation through application files, configuration, or admin interface. Compare against any vendor release notes or version documentation.
    Affected if Version cannot be verified as post-February 2026 or running the patched backend service update
  3. Locate ReviewAnswerDetails PageMethod
    Search the SpeedExam ASP.NET application for the ReviewAnswerDetails PageMethod. This is typically in page code-behind files or AJAX service endpoints within the web application binary or source code.
    Affected if The ReviewAnswerDetails PageMethod exists in the application
  4. Test authorization on ReviewAnswerDetails
    With a low-privilege authenticated account, directly invoke the ReviewAnswerDetails PageMethod with parameters referencing exam records belonging to other users. Observe whether the method returns answer key data without proper authorization.
    Affected if The method returns answer key data for exams the requesting user should not have access to
  5. Inspect server-side authorization code
    Examine the ReviewAnswerDetails PageMethod implementation for server-side authorization checks such as [Authorize] attributes, role validation, or ownership verification before returning any data.
    Affected if No server-side authorization logic is implemented before returning sensitive answer key data

If SpeedExam is deployed and the ReviewAnswerDetails PageMethod returns answer keys to users without proper server-side authorization checks, the environment is affected by this CVE.

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

Apply the vendor's February 2026 backend service update to remediate this vulnerability. Until then, implement server-side authorization validation on the PageMethod and monitor for unauthorized answer key access.

Recommended fix Moderate confidence

SpeedExam Online Examination System (SaaS) - February 2026 backend service update

  1. Contact SpeedExam vendor to confirm your SaaS instance has received the February 2026 backend service update.
  2. Verify with the vendor that the ReviewAnswerDetails PageMethod now enforces proper server-side authorization checks.
  3. Request confirmation from the vendor that client-side restrictions cannot be bypassed for accessing answer keys.
  4. If on a self-hosted version, ensure you have upgraded to the release containing the February 2026 backend fixes.
Caveat As this is a SaaS product, the vendor manages updates; confirm with them that existing integrations or workflows are unaffected

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30707 — 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-30707 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