dbcve.org
Firma RehberiApplication · Web Ofisi

CVE-2019-25458

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
Web Ofisi Firma Rehberi v1 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through GET parameters. Attackers can send requests to with malicious payloads in the 'il', 'kat', or 'kelime' parameters to extract sensitive database information or perform time-based blind SQL injection attacks.

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 confidence

Web Ofisi Firma Rehberi v1 has a critical SQL injection vulnerability in multiple GET parameters ('il', 'kat', 'kelime'). Unauthenticated remote attackers can inject arbitrary SQL commands through these parameters, potentially allowing full database compromise, data exfiltration, or time-based blind SQL injection attacks.

MitigationImplement parameterized queries (PreparedStatement) for all database interactions, especially for the 'il', 'kat', and 'kelime' parameters. Validate and sanitize all user inputs, apply input validation, and consider deploying a WAF as a defense-in-depth measure.

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
Firma RehberiApplication
Affected:= 1.0.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
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 checks

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

  1. Confirm Web Ofisi Firma Rehberi installation
    Locate the application files on your web server. Look for directories or files containing 'firma-rehberi' or 'Web Ofisi' branding. Check for index.php or similar entry points.
    Affected if The software is present on your server and matches version 1.0.0 or earlier versions of the v1 branch.
  2. Identify vulnerable parameter handlers
    Search the application source code for occurrences of the GET parameters 'il', 'kat', and 'kelime'. Use grep or a text search tool to find where these parameters are processed in PHP files.
    Affected if Code references to $_GET['il'], $_GET['kat'], or $_GET['kelime'] exist without proper input sanitization.
  3. Inspect database query patterns
    Examine the PHP files handling those parameters. Look for SQL query construction where these parameters are concatenated directly into query strings, such as 'SELECT * FROM table WHERE il=' . $_GET['il'].
    Affected if String concatenation or interpolation of these GET parameters into SQL statements is found without prepared statements or parameter binding.
  4. Test for SQL injection manually
    Send a crafted GET request with a single quote in each parameter separately: /?il=' or /?kat=' or /?kelime='. Observe if the application returns a MySQL error message in the response.
    Affected if The application returns database error messages containing SQL syntax details when special characters are submitted in these parameters.
  5. Verify authentication requirements
    Attempt the SQL injection tests from an unauthenticated browser session or using a tool like curl without any session cookies or authentication tokens.
    Affected if The SQL injection is exploitable without requiring any login, session, or authentication credentials.

You are affected if Web Ofisi Firma Rehberi v1.0.0 is installed and the 'il', 'kat', or 'kelime' GET parameters are used in unsanitized SQL queries accessible without authentication.

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

Implement parameterized queries (PreparedStatement) for all database interactions, especially for the 'il', 'kat', and 'kelime' parameters. Validate and sanitize all user inputs, apply input validation, and consider deploying a WAF as a defense-in-depth measure.

Fix this in Firma Rehberi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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