dbcve.org
Online Notice BoardApplication · 1000projects

CVE-2025-5650

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-05
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 classified as critical was found in 1000projects Online Notice Board 1.0. This vulnerability affects unknown code of the file /register.php. The manipulation of the argument fname leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.

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 /register.php file of Online Notice Board 1.0 allows remote attackers to inject malicious SQL queries via the fname parameter. The lack of input sanitization or parameterized queries in the registration form enables attackers to manipulate database queries, potentially leading to unauthorized data access, authentication bypass, or complete database compromise.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries in register.php and all affected files. Apply input validation and output encoding. Conduct a comprehensive code audit to identify and remediate additional SQL injection points in the application.

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 Notice BoardApplication
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 Online Notice Board installation
    Search the webroot for the presence of 'register.php' and other Notice Board application files. Common paths: /var/www/html/, /htdocs/, or the web server document root. Look for files like index.php, register.php, and admin/ directories typical of this application.
    Affected if The application '1000projects Online Notice Board' is found in the environment.
  2. Verify the installed version is 1.0
    Check for version indicators in the application. Look in index.php, about.php, or a README file for version strings. Compare the found version against the affected range: 1.0
    Affected if The installed version is exactly 1.0.
  3. Locate and inspect register.php
    Find register.php in the web directory structure. Open the file and examine the code handling the 'fname' parameter in the registration form.
    Affected if The file register.php exists and contains a registration form that accepts a 'fname' parameter.
  4. Check fname parameter for SQL injection vulnerability
    In register.php, search for the SQL query that processes the 'fname' input. Look for code that directly concatenates the fname value into a SQL statement without using prepared statements, parameterized queries, or input sanitization.
    Affected if The code directly inserts the fname parameter into a SQL query without using prepared statements or binding parameters.
  5. Determine if the application is network-accessible
    Verify the web server configuration exposes register.php to network requests. Check if the application accepts external HTTP POST requests to /register.php.
    Affected if The register.php file is accessible over the network and accepts user input.

If Online Notice Board version 1.0 is installed and register.php is network-accessible with unsanitized fname parameter handling, the environment is affected by CVE-2025-5650.

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 prepared statements/parameterized queries in register.php and all affected files. Apply input validation and output encoding. Conduct a comprehensive code audit to identify and remediate additional SQL injection points in the application.

Fix this in Online Notice Board Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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