dbcve.org
Construction Management SystemApplication · Angeljudesuarez

CVE-2024-50972

HIGH · 7.2 CVSS v3.1 Published 2024-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 SQL injection vulnerability in printtool.php of Itsourcecode Construction Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the borrow_id parameter.

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 confidence

SQL injection vulnerability in printtool.php of Itsourcecode Construction Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the borrow_id parameter. The parameter is not properly sanitized or parameterized, enabling attackers to inject malicious SQL queries.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the borrow_id parameter in printtool.php. Implement proper input validation and escaping. Conduct a comprehensive code review of other files in the application for similar SQL injection vulnerabilities.

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
Construction Management 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 the application installation
    Locate the Construction Management System installation directory; look for files named 'printtool.php', 'index.php', or other PHP files containing references to 'Construction Management System' or 'borrow_id'. Identify the web root where the application is hosted.
    Affected if The application 'Angeljudesuarez' or 'Itsourcecode Construction Management System' is installed on the server.
  2. Verify the product version
    Inspect version information in the application, typically found in a README file, about page, or within PHP source files (search for 'version', '1.0', or version constants). Check the header/meta tags of index.php or other entry points.
    Affected if The installed version is exactly 1.0.
  3. Locate the vulnerable file
    Navigate to the application directory and search for the file 'printtool.php'. Common paths may include /admin/, /functions/, or the root directory. Use: find . -name 'printtool.php' or locate the file via file manager.
    Affected if The file printtool.php exists in the application installation.
  4. Check for borrow_id parameter usage
    Open printtool.php and search for 'borrow_id' in the code. Examine how this parameter is handled - look for SQL queries (SELECT, INSERT, UPDATE, DELETE) that incorporate this parameter without using prepared statements or parameter binding.
    Affected if The printtool.php file contains code that processes the 'borrow_id' parameter in a SQL query without prepared statements or proper sanitization.
  5. Confirm lack of input sanitization
    Review the printtool.php source code around the borrow_id handling. Look for functions like mysqli_prepare, PDO::prepare, or any input validation/filtering functions applied to this parameter before constructing SQL queries.
    Affected if The borrow_id parameter is used directly in SQL queries without mysqli_prepare, PDO::prepare, or any input validation/sanitization functions.

A user is affected if they have Angeljudesuarez/Itsourcecode Construction Management System version 1.0 installed with the printtool.php file containing unsanitized borrow_id parameter in SQL queries.

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 for the borrow_id parameter in printtool.php. Implement proper input validation and escaping. Conduct a comprehensive code review of other files in the application for similar SQL injection vulnerabilities.

Fix this in Construction Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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