CVE-2022-3714
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 · uneditedA vulnerability classified as critical has been found in SourceCodester Online Medicine Ordering System 1.0. Affected is an unknown function of the file admin/?page=orders/view_order. The manipulation of the argument id leads to sql injection. It is possible to launch the attack remotely. VDB-212346 is the identifier assigned to this vulnerability.
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 confidenceSQL injection vulnerability in SourceCodester Online Medicine Ordering System 1.0 allows remote attackers to inject malicious SQL commands via the id parameter in the admin/?page=orders/view_order page. The application fails to properly sanitize user input before using it in database queries.
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.
-
Confirm application identity and versionInspect the application's source code, readme files, or access any version information page to identify if it is the Online Medicine Ordering System and determine if the version is 1.0Affected if The installed application is Oretnom23 Online Medicine Ordering System version 1.0
-
Verify admin panel accessibilityNavigate to the admin login page (typically at /admin or /admin/login) and attempt to access the administrative interfaceAffected if The admin panel is accessible without proper access controls
-
Locate the view_order functionalityAccess the orders management page by navigating to admin/?page=orders/view_order in a web browserAffected if The admin/?page=orders/view_order endpoint exists and responds to requests
-
Check id parameter handling in view_orderExamine the server-side source code for the orders/view_order page (typically in a PHP file within the admin or pages directory) and inspect how the id parameter is used in database queriesAffected if The id parameter from the URL is directly concatenated into SQL queries without sanitization or prepared statements
If running version 1.0 of the Online Medicine Ordering System and the admin/?page=orders/view_order page is accessible with an unsanitized id parameter used in SQL queries, the environment is affected by CVE-2022-3714.
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.
dbcve · scopedReplace dynamic SQL queries with parameterized queries or prepared statements. Apply input validation on all user-supplied parameters and apply the vendor patch when available.
- Locate the file containing the view_order function that handles the 'id' parameter (likely in the admin directory or controller)
- Replace direct string concatenation in SQL queries with parameterized queries/prepared statements
- If using MySQLi: Replace $sql = "SELECT * FROM orders WHERE id = '" . $_GET['id'] . "'" with $stmt = $conn->prepare("SELECT * FROM orders WHERE id = ?"); $stmt->bind_param("i", $_GET['id']);
- If using PDO: Replace with $stmt = $conn->prepare("SELECT * FROM orders WHERE id = :id"); $stmt->bindParam(':id', $_GET['id']);
- Alternatively, implement input validation: cast the id parameter to integer using (int)$_GET['id'] if the id should always be numeric
- Test the fix by attempting basic SQL injection payloads in the id parameter (e.g., ' OR '1'='1)
- Restrict admin panel access to trusted IP addresses using .htaccess or server configuration as an additional layer of defense
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3714 — 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-3714 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