CVE-2022-48149
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 · uneditedOnline Student Admission System in PHP Free Source Code 1.0 was discovered to contain a SQL injection vulnerability via the username parameter.
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 the Online Student Admission System PHP version 1.0 allows injection through the username parameter. The application fails to properly sanitize user input before using it in SQL queries, enabling attackers to manipulate database queries and potentially exfiltrate or modify sensitive admission data.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify application versionLocate the Online Student Admission System installation directory and check for version files, README, or a version constant in the source code (often in files like version.php, config.php, or in the main index file). Compare the found version to 1.0.Affected if The installed version is exactly 1.0 (as specified in the affected versions)
-
Locate authentication codeFind the login or authentication handler script in the application (commonly named login.php, auth.php, or similar in the admin or user directory). This is where the username parameter would be processed.Affected if The application uses a login mechanism that accepts a username parameter
-
Examine username parameter handlingOpen the authentication script and locate the code that processes the username input from POST or GET requests. Look for how this parameter is incorporated into SQL queries.Affected if The username parameter is directly concatenated into an SQL query string without using prepared statements or parameter binding
-
Check for SQL injection mitigationsSearch the authentication code for use of mysqli_prepare, PDO::prepare, or similar parameterized query functions. Verify that the username variable is passed as a bound parameter rather than string concatenation.Affected if The code uses direct string concatenation (like $sql = "SELECT * FROM users WHERE username = '" . $username . "'") instead of prepared statements
-
Test vulnerability existenceIf you have a test environment, attempt a simple SQL injection payload in the username field during login (e.g., ' OR '1'='1). Observe if the application returns unexpected results or database errors.Affected if The application accepts the injection payload without proper sanitization or returns SQL error messages revealing database structure
You are affected if you are running Online Student Admission System version 1.0 and the username parameter in the login functionality is handled via direct string concatenation in SQL queries rather than parameterized prepared statements.
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 dataReplace dynamic SQL query construction with parameterized queries/prepared statements in all authentication-related code paths. Validate and sanitize all user inputs, particularly the username parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48149 — 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-2022-48149 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