/

CVE-2025-70146

Severity:

CRITICAL RISK

(9.1)

Missing Authentication / Authorization in ProjectWorlds

CVE-2025-70146

Analyzed

Vulnerability type

Category:

Missing Authentication / Authorization

CWE:

CWE-306, CWE-862

Impact:

Unauthorized Administrative Access and Data Manipulation

Severity:

CRITICAL RISK

(9.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

ProjectWorlds Online Time Table Generator 1.0 exposes multiple administrative actions under the /admin/ directory without enforcing authentication.

Remote attackers can directly invoke these admin endpoints via crafted HTTP requests to add, delete, or modify records without having a valid session.

Affected context

The vulnerability occurs in the web application's administrative area, specifically in scripts located under the /admin/ path.

These endpoints are intended for authenticated administrators to manage timetable-related data, but the implementation does not consistently verify that a user is logged in or has admin privileges.

In deployments where the admin interface is reachable over the network (e.g., exposed to the internet or a large internal network), any remote user who can access the application URL may be able to trigger these administrative actions directly.

Exploit preconditions

  • Attack surface: HTTP(S) endpoints under /admin/ in the Online Time Table Generator 1.0 application.
  • Required access: Network-level access to the web server; no valid user account or session is required.
  • Trigger point: Sending direct HTTP requests (e.g., GET/POST) to vulnerable admin scripts that perform operations such as adding or deleting records.
  • Why exploitation is possible: The application does not enforce authentication or session checks on these admin-only scripts (CWE-306), and fails to ensure that the caller has appropriate authorization for the requested action (CWE-862).

Why this happens

The core issue is the absence of robust access control on administrative functions.

Administrative scripts under /admin/ execute sensitive operations based solely on the incoming request parameters, without validating that the requester has an active authenticated session or appropriate privileges.

This pattern maps to CWE-306: Missing Authentication for Critical Function, where critical capabilities are exposed without login, and CWE-862: Missing Authorization, where the system does not verify that the user is permitted to perform the requested action.

Architecturally, the access control logic is either missing, inconsistently applied, or implemented only in some parts of the admin UI but not in the underlying action endpoints.

Potential impact

  • Attackers may add arbitrary timetable records, including fake classes, rooms, or schedules.
  • Attackers may delete or modify existing records, disrupting normal operations.
  • Attackers can potentially escalate impact by abusing admin operations to access or reorganize sensitive information.
  • The integrity and reliability of scheduling data can be compromised, leading to operational confusion or downtime.
  • Audit trails and logs may be rendered unreliable due to unauthorized changes performed under no or incorrect identity.

General mitigation guidance

Effective mitigation focuses on implementing centralized, consistent access control for all administrative functionality:

  • Introduce mandatory authentication checks for every script and controller under /admin/, enforcing that only authenticated users can access them.
  • Apply role-based or permission-based authorization so that only designated administrator roles can invoke critical operations such as create, update, and delete actions.
  • Use a common middleware, filter, or front-controller pattern that performs session and privilege checks before any admin business logic executes, rather than relying on per-script ad hoc checks.
  • Restrict network exposure of the admin interface (e.g., IP allowlisting, VPN-only access, or segregated admin hostnames) to reduce the reachable attack surface.
  • Follow the principle of least privilege in database and application layers so that even if a path is misconfigured, backend components are not broadly exposed to destructive operations.

How teams detect issues like this

Detection generally combines code-level review and runtime monitoring:

  • Static analysis / code review:
  • Search for admin scripts, controllers, or routes (e.g., under /admin/) that invoke database write operations or sensitive business logic without prior session or role checks.
  • Look for patterns where request-handling code directly performs inserts, updates, or deletes before any authentication middleware is invoked.
  • Verify that all admin routes are registered behind an authentication/authorization layer in the routing configuration or framework.
  • Policy and configuration review:
  • Inspect web server and application routing to ensure /admin/ paths are not excluded from authentication mechanisms.
  • Confirm that there is a single, enforced entry point for admin access instead of multiple unaudited action scripts.
  • Runtime/monitoring:
  • Monitor logs for anonymous or unauthenticated requests successfully invoking admin endpoints or performing data-changing operations.
  • Use security testing tools or automated scanners to probe for admin URLs accessible without logging in.

Sources

SourceLink
projectworlds.comprojectworlds.com/online-time-table-generator-php-mysql/
youngkevinn.github.ioyoungkevinn.github.io/posts/CVE-2025-70146-OTTTG-Unauth-Deletion/

Frequently asked

questions

Yes. As long as the admin paths are reachable over the network, an attacker can exploit this issue remotely without needing to authenticate.

No. The weakness stems from missing authentication and authorization checks on the admin scripts, so any network user can attempt to call these endpoints directly.

Enforce centralized authentication and authorization for all administrative endpoints, ensuring that every request to /admin/ passes through a common access control layer that verifies identity and privileges before executing the action.

Design access control as a core framework feature rather than per-script logic: route all sensitive operations through authenticated controllers, apply least privilege roles, include automated tests that verify admin URLs are not accessible without login, and incorporate security-focused code review or automated checks targeting access control gaps.

Find out what's already
exploitable in your codebase.