dbcve.org
Online Job Search EngineApplication · Fabian

CVE-2025-12928

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-10
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
A vulnerability was detected in code-projects Online Job Search Engine 1.0. This affects an unknown function of the file /login.php. Performing manipulation of the argument username/phone results in sql injection. The attack is possible to be carried out remotely. The exploit is now 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 confidence

SQL injection vulnerability in the login.php file of code-projects Online Job Search Engine 1.0 allows remote attackers to inject malicious SQL queries through the username/phone parameter on the login form. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries, potentially leading to unauthorized access, data exfiltration, or complete database compromise.

MitigationImmediately disable or restrict access to the login.php page until remediation is complete. Implement parameterized queries or prepared statements for all database operations involving user input (username/phone), apply input validation, and consider deploying a WAF rule as a temporary protective 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
Online Job Search EngineApplication
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
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. Identify the Online Job Search Engine installation
    Locate the web application directory on your server - typically found in web root folders (htdocs, www, public_html). Look for files named 'login.php', 'index.php', or folders containing 'job' or 'search' in the name.
    Affected if The application directory contains the Online Job Search Engine by Fabian (version 1.0)
  2. Confirm the installed version
    Check for a version file, README, or footer in the application that displays the version number. Compare this against version 1.0.
    Affected if The installed version is exactly 1.0 ( Fabian Online Job Search Engine )
  3. Verify login.php exists and is accessible
    Check for the presence of login.php in the application root or /admin/ folder. Confirm it is accessible via HTTP/HTTPS.
    Affected if login.php file exists and responds to web requests
  4. Examine login.php for vulnerable code patterns
    Open login.php in a text editor and search for SQL query construction patterns. Look for direct concatenation of the username/phone parameter into SQL statements without using prepared statements, parameterized queries, or proper escaping.
    Affected if The code contains SQL queries that directly incorporate the username/phone parameter without prepared statements or input sanitization (e.g., "SELECT * FROM users WHERE username = '" . $_POST['username'] . "'")
  5. Test the login form for SQL injection
    Submit a SQL injection payload in the username/phone field of the login form (e.g., "' OR '1'='1" or "' OR 1=1--"). Observe if the application returns unexpected database errors, behaves differently than normal login attempts, or grants unauthorized access.
    Affected if The login form responds to SQL injection payloads with database errors, authentication bypass, or unexpected behavior indicating the parameter is not properly sanitized

You are affected if the Fabian Online Job Search Engine version 1.0 is installed and the login.php file contains direct SQL query construction using the username/phone parameter without prepared statements.

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

Immediately disable or restrict access to the login.php page until remediation is complete. Implement parameterized queries or prepared statements for all database operations involving user input (username/phone), apply input validation, and consider deploying a WAF rule as a temporary protective measure.

Fix this in Online Job Search Engine Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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