dbcve.org
I DoitApplication

CVE-2019-1010248

CRITICAL · 9.8 CVSS v3.0 Published 2019-07-18
Fix available
A fix is available. Upgrade to after 1.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Synetics GmbH I-doit 1.12 and earlier is affected by: SQL Injection. The impact is: Unauthenticated mysql database access. The component is: Web login form. The attack vector is: An attacker can exploit the vulnerability by sending a malicious HTTP POST request. The fixed version is: 1.12.1.

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 the web login form of I-doit 1.12 and earlier allows unauthenticated attackers to inject malicious SQL queries via HTTP POST request, potentially granting full access to the underlying MySQL database.

MitigationUpgrade I-doit to version 1.12.1 or later to remediate the SQL injection vulnerability.

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
I DoitApplication
Affected:<= 1.12

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
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify I-doit version from web interface
    Log into the I-doit web portal as an administrator. Navigate to the administration or system settings area, typically found under 'Admin' > 'System settings' or 'About' page. Locate the version information displayed there.
    Affected if The displayed version is 1.12 or any earlier version (e.g., 1.11, 1.10, etc.)
  2. Identify I-doit version from source files
    If you have direct server access, locate the I-doit installation directory. Look for a version file, changelog, or composer.json that contains the software version. Common locations include the root directory or a 'src' or 'vendor' folder.
    Affected if The version found in source files is 1.12 or earlier
  3. Confirm web login form is accessible
    Attempt to access the I-doit login page via HTTP/HTTPS. The typical path is /idoit/ or /src/ at your domain. Verify the login form loads without authentication required.
    Affected if The login form loads without requiring authentication, indicating the attack surface is exposed
  4. Check if application is using default database configuration
    Examine the database configuration file (often named config.inc.php or similar in the I-doit installation directory) to confirm MySQL is in use and the application connects to the database.
    Affected if The application connects to a MySQL database, which is the target of the SQL injection vulnerability

You are affected if your I-doit installation is version 1.12 or earlier and the web login form is accessible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.12
Interim mitigation

Upgrade I-doit to version 1.12.1 or later to remediate the SQL injection vulnerability.

Recommended fix High confidence

I-doit 1.12.1

  1. 1. Backup the existing I-doit installation and MySQL database before proceeding with the upgrade.
  2. 2. Download I-doit version 1.12.1 from the official source (sourceforge.net) or the vendor's website.
  3. 3. Extract the new version files to replace the existing installation, preserving configuration files and customizations.
  4. 4. Run any database migration scripts included in the 1.12.1 release to update the database schema.
  5. 5. Verify that the web server is properly serving the updated application files.
  6. 6. Test the login functionality to ensure the application is working correctly after the upgrade.
  7. 7. Confirm that the SQL injection vulnerability is no longer present by verifying the login form properly sanitizes input.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in I Doit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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