dbcve.org
TestlinkApplication

CVE-2015-7390

CRITICAL · 9.8 CVSS v3.0 Published 2017-09-26
Fix available
A fix is available. Upgrade to after 1.9.13 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
SQL injection vulnerability in TestLink before 1.9.14 allows remote attackers to execute arbitrary SQL commands via the apikey parameter to lnl.php.

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 TestLink's lnl.php script allows unauthenticated remote attackers to inject malicious SQL commands through the apikey parameter, potentially exposing or manipulating the entire database.

MitigationUpgrade to TestLink 1.9.14 or later, or implement parameterized queries/prepared statements for the apikey parameter in lnl.php with input validation to remediate this critical 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
TestlinkApplication
Affected:<= 1.9.13

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. Locate TestLink installation
    Search web server document root directories for testlink folder (common paths: /var/www/html/testlink, /var/www/testlink, /htdocs/testlink) or check for lnl.php file in web-accessible directories
    Affected if TestLink is found in the environment
  2. Identify TestLink version
    Open the version.php file in the TestLink root directory (e.g., /var/www/html/testlink/version.php) and read the $g_version or VERSION constant
    Affected if The version displayed is 1.9.13 or earlier
  3. Verify lnl.php exists and is accessible
    Check for the presence of lnl.php in the TestLink web root (e.g., testlink/lnl.php) - this file handles API login functionality
    Affected if lnl.php exists and is web-accessible
  4. Check apikey parameter handling in lnl.php
    Review the lnl.php source code and locate the code handling the 'apikey' GET or POST parameter - look for direct insertion into SQL queries without prepared statements or escaping
    Affected if The apikey parameter is used in SQL queries without parameterized statements or input validation (vulnerable code pattern: $db->exec_query($sql with $apikey directly inserted)
  5. Confirm vulnerability through affected version
    If you cannot review code, confirm the installed TestLink version by accessing the About page or checking config.php for version numbers
    Affected if The confirmed version is 1.9.13 or lower AND lnl.php handles the apikey parameter

You are affected if TestLink is installed with version 1.9.13 or earlier and the lnl.php file handling the apikey parameter is accessible without code modifications to prevent SQL injection.

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.9.13
Interim mitigation

Upgrade to TestLink 1.9.14 or later, or implement parameterized queries/prepared statements for the apikey parameter in lnl.php with input validation to remediate this critical vulnerability.

Recommended fix High confidence

TestLink 1.9.14

  1. 1. Backup the TestLink database and all configuration files before proceeding.
  2. 2. Download TestLink version 1.9.14 from the official TestLink repository or website.
  3. 3. Replace the existing TestLink installation files with the new version 1.9.14 files.
  4. 4. Run any database migration scripts included in the upgrade package.
  5. 5. Verify the upgrade was successful by logging into TestLink.
  6. 6. Confirm the lnl.php file has been updated and the apikey parameter is now properly sanitized.
Caveat Review release notes for any configuration changes required between 1.9.13 and 1.9.14

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

Fix this in Testlink Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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