dbcve.org
Online Admission SystemApplication · Projectworlds

CVE-2025-8471

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
A vulnerability, which was classified as critical, has been found in projectworlds Online Admission System 1.0. This issue affects some unknown processing of the file /adminlogin.php. The manipulation of the argument a_id leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

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

SQL injection vulnerability in projectworlds Online Admission System 1.0's adminlogin.php file. The a_id parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. With CVSS 9.8, this can lead to complete database compromise, including unauthorized admin access and data exfiltration.

MitigationImmediately restrict network access to the adminlogin.php endpoint. Implement parameterized queries/prepared statements for all database interactions, particularly the a_id parameter. Conduct a comprehensive code review to identify and remediate similar SQL injection vulnerabilities throughout the application.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Online Admission SystemApplication
Affected:= 1.0

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

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

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 Online Admission System installation
    Search for the adminlogin.php file in your web root directories. Common paths include /admin/, /adminlogin.php, or within a project folder named 'online-admission-system'. Use: find /var/www -name 'adminlogin.php' 2>/dev/null or dir /s /b C:\inetpub\adminlogin.php
    Affected if The adminlogin.php file from projectworlds Online Admission System is found on the server
  2. Verify the product version
    Check for version indicators such as a version.php file, footer copyright text, or a meta tag in the main index file. The affected version is 1.0. Look for strings like 'Version 1.0' or 'Online Admission System v1.0' in source code
    Affected if The installed version is 1.0 or cannot be determined (treat as affected)
  3. Check if adminlogin.php is web-accessible
    Attempt to access the adminlogin.php file via HTTP/HTTPS from a browser or curl. The vulnerable URL pattern is: http(s)://<your-domain>/adminlogin.php or http(s)://<your-domain>/<path>/adminlogin.php
    Affected if The adminlogin.php page loads or responds to web requests (endpoint is exposed)
  4. Inspect the a_id parameter handling in source code
    Open adminlogin.php in a text editor and locate the code handling the 'a_id' parameter. Look for unsanitized SQL queries, typically patterns like: $query = "SELECT * FROM ... WHERE a_id='$a_id'" or similar string concatenation without escaping functions or prepared statements
    Affected if The code shows direct insertion of the a_id parameter into SQL queries without using prepared statements, mysqli_prepare, or PDO parameterized queries

You are affected if the Online Admission System version 1.0 is installed, the adminlogin.php file is web-accessible, and the source code contains unsanitized SQL queries using the a_id parameter.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict network access to the adminlogin.php endpoint. Implement parameterized queries/prepared statements for all database interactions, particularly the a_id parameter. Conduct a comprehensive code review to identify and remediate similar SQL injection vulnerabilities throughout the application.

Fix this in Online Admission System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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