CVE-2026-36948
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 · uneditedSourcecodester Online Thesis Archiving System v1.0 is vulnerale to SQL injection in the file /otas/view_archive.php.
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 · moderate confidenceSQL injection vulnerability in /otas/view_archive.php of Sourcecodester Online Thesis Archiving System v1.0 allows attackers to manipulate database queries through unsanitized input, potentially enabling unauthorized data access, modification, or extraction.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the view_archive.php fileSearch for the file /otas/view_archive.php in the web root directory. Common paths include /var/www/html/otas/view_archive.php or C:\xampp\htdocs\otas\view_archive.phpAffected if The file exists in the expected location within the web application directory
-
Verify the application versionCheck for version information in the application (typically in an about page, readme file, or meta tags in main pages). Compare against v1.0Affected if The installed version is Sourcecodester Online Thesis Archiving System v1.0
-
Inspect view_archive.php for SQL query handlingOpen view_archive.php and examine database query code. Look for SQL statements that use $_GET, $_POST, or $_REQUEST parameters directly in queries without prepared statements, parameterized queries, or input sanitization functions like mysqli_real_escape_string or PDO quote()Affected if The file contains SQL queries that directly incorporate user-supplied input (e.g., $_GET['id'] or $_POST['parameter']) without using prepared statements or escaping functions
-
Identify vulnerable parameter usageIn view_archive.php, locate all database query functions (mysqli_query, PDO::query, mysql_query) and trace whether any parameters come from user input (GET/POST/REQUEST) and are concatenated or interpolated into SQL stringsAffected if User-controlled parameters from HTTP requests are concatenated directly into SQL query strings without binding or escaping
-
Confirm database is accessibleVerify the application has an active database connection (MySQL/MariaDB) and the view_archive.php page can be accessed via HTTP to test parameter injectionAffected if The application connects to a database and view_archive.php is accessible as a web-accessible endpoint
A user is affected if they have Sourcecodester Online Thesis Archiving System v1.0 installed with view_archive.php accessible, and that file contains SQL queries that directly use unsanitized user input from HTTP requests.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement prepared statements/parameterized queries with proper input validation and sanitization for all user-supplied parameters in view_archive.php before using them in database operations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36948 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36948 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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