Academic & Examination Platform Security Assessment Playbook
1. Overview & Scope
This skill provides a structured methodology for auditing Computer-Based Testing (CBT), Learning Management Systems (LMS), and online examination portals. These applications frequently manage high-stakes evaluation data, student records, and timed workflows that depend heavily on state machine integrity.
Primary Vulnerability Classes (OWASP WSTG)
- WSTG-ATHZ-04: Insecure Direct Object References (IDOR / BOLA) on question banks and student answers.
- WSTG-INFO-05: Sensitive Data Exposure in Single Page Application (SPA) client bundles and un-rendered JSON states.
- WSTG-BUSL-01/02: Business Logic Flaws & State Machine bypasses in multi-stage exam workflows.
- WSTG-BUSL-08: Client-Side Timing & Clock Manipulation vs Server-Side Epoch Timestamp enforcement.
2. Assessment Methodology
Phase 1: Passive Reconnaissance & State Analysis
- Frontend Architecture Fingerprinting:
- Identify whether the portal is a Single Page Application (React, Vue, Next.js, Angular) or traditional server-rendered template.
- Inspect JavaScript bundles (
/static/js/*.jsor_next/static/chunks/*.js) for unminified state models or route schemas.
- Payload & Model Review:
- Check if exam questions fetched from
/api/v1/session/{id}or GraphQL endpoints include premature fields (correct_option,answer_key,explanation,solution). - Run the Cybermes diagnostic tool:
python3 scripts/audit_exam_state_machine.py --url https://exam-portal.example.edu/api/v1/session/101 --token <SESSION_TOKEN>
- Check if exam questions fetched from
Phase 2: State Machine & Workflow Verification (WSTG-BUSL-02)
Standard online exam lifecycle:
[Registration] -> [Verification] -> [Exam Start] -> [Answering] -> [Submission] -> [Scoring]
- Step-Skipping Tests:
- Attempt direct POST/GET to
/api/v1/exam/{id}/submitbefore invoking/api/v1/exam/{id}/start. - Attempt to access results endpoint
/api/v1/exam/{id}/reviewwhile the exam status is stillACTIVE.
- Attempt direct POST/GET to
- Re-submission & Concurrency (Race Conditions):
- Test if sending simultaneous answer submission requests allows overwriting final scores or duplicate grading executions.
Phase 3: Timer & Deadline Integrity (WSTG-BUSL-08)
- Client Clock vs Server Timestamp:
- Check if the timer is enforced client-side (
remaining_timedecremented in JavaScriptsetInterval) or tracked server-side with an immutabledeadline_epoch. - Tamper with local machine time or intercept submission payloads modifying
durationorclient_submitted_atparameters.
- Check if the timer is enforced client-side (
- Late-Submission Acceptance:
- Submit an answer payload 5-10 minutes after the scheduled test window expires.
- Confirm whether the server strictly rejects late entries with HTTP 403 / 409 or silently accepts them.
Phase 4: Access Control & IDOR Testing (WSTG-ATHZ-04)
- Cross-Account Session Isolation:
- Setup two authorized test accounts (Student A and Student B).
- In Student A's active session, replace
session_idorstudent_idwith Student B's identifier inPOST /api/v1/exam/answer. - Verify that the server validates session ownership against the authenticated JWT / session cookie and returns 403 Forbidden.
3. Remediation & Defensive Hardening
- Server-Side Authorization & Ownership:
- Bind every question-fetch and answer-submission strictly to the authenticated user ID extracted from server-validated tokens.
- Never accept
user_idorstudent_idfrom client request bodies.
- Data Model Stripping:
- Separate question entities from answer keys at the database/DTO layer.
- Never serialize
correct_answerorexplanationinto the client-facing question delivery API until the exam period has formally concluded.
- Immutable Server-Side Timer:
- Store
started_atand calculateexpires_at = started_at + durationon the server database. - When a submission arrives, compare
current_server_time <= expires_at + grace_period(e.g. 5 seconds for network latency). Discard late submissions automatically.
- Store
