CVE-2025-8923
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 was determined in code-projects Job Diary 1.0. This vulnerability affects unknown code of the file /edit-details.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public 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 · moderate confidenceSQL injection vulnerability in the ID parameter of /edit-details.php in code-projects Job Diary 1.0 allows remote attackers to inject arbitrary SQL commands. The lack of parameterized queries or input sanitization on the ID argument enables authenticated attackers to manipulate 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 Job Diary installationLocate the Job Diary application on your system. Check for files or directories containing 'job-diary', 'jobdiary', or similar naming.Affected if The application code-projects Job Diary or Anisha Job Diary is present on the system
-
Verify the version is 1.0Check the application version metadata (such as a version file, composer.json, or README) to confirm the installed version is 1.0Affected if The installed version is exactly 1.0
-
Locate edit-details.phpSearch for the file edit-details.php within the Job Diary application directory structureAffected if The file edit-details.php exists in the application
-
Inspect ID parameter handling in edit-details.phpOpen edit-details.php and examine how the ID parameter is used in SQL queries. Search for direct insertion of $_GET['id'] or $_POST['id'] into SQL statements without using prepared statements, parameter binding, or input sanitization functions like mysqli_real_escape_string or PDO::prepare.Affected if The ID parameter is used directly in SQL queries without parameterized queries, binding, or escaping functions
-
Verify authentication is enabledCheck if the application requires authentication to access edit-details.php. Look for session checks, login validation, or authentication middleware at the top of the file.Affected if Authentication is not enforced or can be bypassed for the edit-details.php endpoint
If the installed version is Job Diary 1.0 and edit-details.php contains SQL queries that use the ID parameter without prepared statements or input sanitization, the environment is affected by CVE-2025-8923.
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 in edit-details.php with prepared statements/parameterized queries and implement proper input validation on the ID parameter. Apply principle of least privilege to the database user.
- 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-2025-8923 — 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-2025-8923 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