CVE-2026-5180
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 flaw has been found in SourceCodester Simple Doctors Appointment System 1.0. This vulnerability affects unknown code of the file /admin/ajax.php?action=login2. This manipulation of the argument email causes sql injection. The attack is possible to be carried out remotely. The exploit has been published 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 confidenceSQL injection vulnerability in SourceCodester Simple Doctors Appointment System 1.0 allows remote attackers to inject malicious SQL queries via the email parameter in /admin/ajax.php?action=login2. The application fails to properly sanitize user input before using it in SQL queries.
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.
-
Confirm application and versionLocate the SourceCodesters Simple Doctors Appointment System installation and identify its version number (typically found in about page, footer, or version config file)Affected if Version is 1.0
-
Verify vulnerable file existsCheck if the file /admin/ajax.php exists in the web root directoryAffected if File exists and the login2 action is defined within it
-
Check login2 action implementationExamine /admin/ajax.php for the login2 action handler - look for SQL query construction using the email parameter without prepared statements or sanitizationAffected if The code directly incorporates the email parameter into a SQL query string
-
Verify admin panel accessibilityConfirm the /admin/ajax.php endpoint is accessible over HTTP/HTTPS without authentication restrictionsAffected if Endpoint is reachable and accepts the email parameter in login2 action
-
Test email parameter handlingSend a benign SQL injection test payload (e.g., email parameter set to test' OR '1'='1) to /admin/ajax.php?action=login2 and observe if SQL syntax errors are returnedAffected if Application returns SQL errors or behaves differently than expected with malicious input
If running version 1.0 of SourceCodester Simple Doctors Appointment System and the login2 action in /admin/ajax.php handles the email parameter without parameterized queries, the environment is affected by this CVE.
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 queries with parameterized queries/prepared statements in the login2 action of ajax.php, implement proper input validation on the email parameter, and apply any available vendor patches.
- 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-5180 — 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-5180 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