Summary
ProjectWorlds Online Time Table Generator 1.0 exposes sensitive admin data due to missing authentication checks on /admin/student.php and /admin/teacher.php.
Remote attackers can directly access these endpoints via HTTP GET without a valid session and obtain sensitive information, including plaintext password field values.
Affected context
The vulnerability occurs in the web application's administrative module for managing students and teachers.
Specifically, the student.php and teacher.php scripts under the /admin/ path can be reached directly over HTTP without enforcing a logged-in admin session.
In deployments where these endpoints are Internet-accessible and not additionally protected by network-level controls, any external user can browse to these URLs and view sensitive records.
Exploit preconditions
- Attack surface: Public or internal web interface of the Online Time Table Generator application.
- Required access: Network access to the web server; no login, cookies, or valid session required.
- Trigger point: Direct HTTP GET requests to:
/admin/student.php/admin/teacher.php- Why exploitation is possible: The application does not enforce authentication or authorization on these admin pages, so access control is effectively bypassed and sensitive fields are rendered to unauthenticated users.
Why this happens
This issue stems from a failure to enforce authentication and authorization on sensitive administrative endpoints.
The /admin/student.php and /admin/teacher.php scripts do not check for a valid, authenticated session or user role before executing and returning data.
This aligns with:
- CWE-306: Missing Authentication for Critical Function, where security-sensitive operations are exposed without verifying user identity.
- CWE-862: Missing Authorization, because access to privileged administrative data is not restricted to appropriate roles.
At a design level, the application appears to rely on URL structure (/admin/) rather than consistent server-side session checks as the protection mechanism, which is an insecure pattern.
Potential impact
- Remote attackers can view sensitive student and teacher records.
- Exposure of plaintext password fields, enabling account takeover on this or other systems where users reuse credentials.
- Unauthorized enumeration of users, IDs, and related personal or academic information.
- Facilitation of social engineering and phishing based on harvested identity data.
- Undermining of overall trust and confidentiality for users of the timetable system.
General mitigation guidance
Effective mitigation focuses on enforcing strict, centralized access control for all administrative functionality:
- Require robust authentication (e.g., session-based login) before granting access to any
/admin/endpoint. - Implement role-based authorization checks so that only users with administrative roles can access student and teacher management pages.
- Use a common middleware or controller layer that automatically applies authentication/authorization checks to admin routes, rather than per-file ad hoc logic.
- Avoid storing or displaying passwords in plaintext; instead, use one-way hashing and remove password fields from all UI views where they are not strictly necessary.
- Apply the principle of least privilege, exposing only the minimum required data on each page and redacting sensitive fields by default.
How teams detect issues like this
Detection generally involves a mix of code-level and runtime analysis:
- Code review: Look for admin or privileged scripts (often under
/admin/or similar paths) that do not verify session state or user role before executing. Absence of authentication checks near the top of these scripts is a strong signal. - Static analysis: Configure rules to flag any web routes or controllers containing sensitive operations or database reads of user data that lack calls to the authentication/authorization framework.
- Security testing: Use web application scanners or manual testing to crawl the application and attempt to access admin URLs without logging in; note any pages that respond with data instead of redirecting to a login page.
- Logging and monitoring: Monitor access logs for unauthenticated requests to admin paths and correlate with response codes and sizes to identify endpoints leaking content.

