CVE-2023-32306
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 · uneditedTime Tracker is an open source time tracking system. A time-based blind injection vulnerability existed in Time Tracker reports in versions prior to 1.22.13.5792. This was happening because the `reports.php` page was not validating all parameters in POST requests. Because some parameters were not checked, it was possible to craft POST requests with malicious SQL for Time Tracker database. This issue is fixed in version 1.22.13.5792. As a workaround, use the fixed code in `ttReportHelper.class.php` from version 1.22.13.5792.
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 confidenceA time-based blind SQL injection vulnerability exists in the reports.php page of Time Tracker. The vulnerability stems from improper validation of POST request parameters, allowing attackers to inject malicious SQL queries into the application's database. This affects versions prior to 1.22.13.5792.
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.22.13.5792CVSS 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 installed Anuko Time Tracker versionCheck the version file or header in the application (common locations: VERSION file, config.php, or login page footer). Alternatively, look for version strings in source files like common.php or init.php.Affected if The installed version is less than 1.22.13.5792 (e.g., 1.22.12, 1.21.x, etc.).
-
Locate reports.php fileFind the reports.php file in the web root or application directory. It should be present in standard Anuko Time Tracker installations.Affected if The file exists and the application processes POST requests to it.
-
Check ttReportHelper.class.php for parameter validationExamine ttReportHelper.class.php (or ttReportHelper.php) in the lib or include directory. Look for the code that handles POST parameters passed to reports.php - specifically check if parameters are validated using functions like p() or similar input sanitization before being used in SQL queries.Affected if POST parameters are used directly in database queries without proper validation (e.g., no escaping, no prepared statements, no validation functions).
-
Test for SQL injection vulnerabilityIf you have a test environment, send a crafted POST request to reports.php with SQL injection payload in parameters (e.g., time_tracking parameter with ' AND SLEEP(5)--). Monitor for delayed response indicating time-based injection.Affected if The application responds with a time delay corresponding to injected SLEEP() or similar time-based SQL functions.
You are affected if your installed Anuko Time Tracker version is below 1.22.13.5792 AND the application processes POST requests to reports.php without proper parameter validation in ttReportHelper.class.php.
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 · scoped1.22.13.5792
Upgrade to version 1.22.13.5792 or apply the parameter validation fix from ttReportHelper.class.php to ensure all POST parameters are properly validated before database queries.
1.22.13.5792
- Download Time Tracker version 1.22.13.5792 or later from the official repository
- Backup the existing database and application files before upgrading
- Install or replace the application files with version 1.22.13.5792
- Verify that ttReportHelper.class.php contains the fixed code with proper parameter validation for POST requests
- Test the reports.php functionality to confirm the SQL injection vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32306 — 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-2023-32306 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