dbcve.org
Task Reminder SystemApplication · Oretnom23

CVE-2023-5813

HIGH · 8.8 CVSS v3.1 Published 2023-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 was found in SourceCodester Task Reminder System 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /classes/Master.php?f=delete_reminder. The manipulation of the argument id leads to sql injection. The attack may be launched remotely. The identifier of this vulnerability is VDB-243644.

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 confidence

SQL injection vulnerability in the delete_reminder function of /classes/Master.php in SourceCodester Task Reminder System 1.0 allows remote attackers to inject malicious SQL queries via the unsanitized id parameter in the delete_reminder functionality.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) to properly sanitize the id parameter before executing database operations.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Task Reminder System installation
    Locate the application files and identify the version. Check for /classes/Master.php file which contains the Master class. Look for version identifier in README, about page, or version config file.
    Affected if The application is SourceCodester/Oretnom23 Task Reminder System version 1.0
  2. Locate the vulnerable file
    Inspect the file /classes/Master.php in the application root directory. Open the file and search for the delete_reminder function definition.
    Affected if The file /classes/Master.php exists and contains a delete_reminder function
  3. Verify vulnerable SQL construction
    Examine the delete_reminder function code in Master.php. Look for SQL queries that concatenate or embed the id parameter directly into the query string without using prepared statements or parameter binding.
    Affected if The delete_reminder function contains SQL query construction that uses the id parameter without sanitization (e.g., string concatenation into SQL)
  4. Check if delete_reminder is accessible
    Determine if there is a web route, endpoint, or form that calls the delete_reminder function. Check the application's routing configuration or any file that invokes this function via HTTP request.
    Affected if The delete_reminder function can be invoked through a web request (API endpoint, form action, or AJAX call) with user-controlled id parameter
  5. Verify database connectivity
    Confirm the application connects to a MySQL database. Check the database configuration file (usually in /config/ or /application/config/) for database credentials and connection parameters.
    Affected if The application uses MySQL database and the delete_reminder function executes queries against it

The environment is affected if the Task Reminder System 1.0 is installed with the /classes/Master.php file containing the vulnerable delete_reminder function that processes unsanitized id parameters from web requests.

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

Replace dynamic SQL queries with parameterized queries (prepared statements) to properly sanitize the id parameter before executing database operations.

Fix this in Task Reminder System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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