dbcve.org
Online Notes Sharing PlatformApplication · Projectworlds

CVE-2025-8946

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-14
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 has been found in projectworlds Online Notes Sharing Platform 1.0. This vulnerability affects unknown code of the file /login.php. The manipulation of the argument User leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the 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 · high confidence

SQL injection vulnerability in projectworlds Online Notes Sharing Platform 1.0's /login.php file allows remote attackers to inject malicious SQL commands via the User parameter, potentially enabling unauthorized database access, authentication bypass, or data exfiltration.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in login.php, apply strict input validation on the User parameter, and restrict database user privileges to minimize blast radius.

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 Notes Sharing PlatformApplication
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. Confirm Projectworlds Online Notes Sharing Platform installation
    Locate the web application's root directory and verify the presence of the Online Notes Sharing Platform application files.
    Affected if The application is not present or is a different product entirely.
  2. Verify application version is 1.0
    Check for version indicators in the application - look for version files, about pages, or check the source code comments/headers that may display the version number.
    Affected if The installed version is 1.0 exactly.
  3. Locate the login.php file
    Navigate to the web root directory and verify the existence of the login.php file at /login.php path.
    Affected if The login.php file exists at the expected path.
  4. Inspect the User parameter handling in login.php
    Open login.php and locate the code that processes the User parameter - look for SQL query construction that uses this parameter without parameterized queries or input sanitization.
    Affected if The User parameter is used in a SQL query without prepared statements, parameter binding, or input validation functions.
  5. Test for SQL injection vulnerability
    Submit a SQL injection test payload (such as a single quote or common SQLi patterns) to the User parameter in login.php and observe the application's response for SQL errors or unexpected behavior.
    Affected if The application returns SQL error messages or behaves differently than expected when malformed input is provided.

The environment is affected if Projectworlds Online Notes Sharing Platform version 1.0 is installed, login.php exists, and the User parameter is handled in SQL queries without parameterized statements or input validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries or prepared statements in login.php, apply strict input validation on the User parameter, and restrict database user privileges to minimize blast radius.

Recommended fix High confidence
  1. 1. Do not use this software in production environments - it is an educational/example project without security support.
  2. 2. If already deployed, take the system offline immediately to prevent exploitation.
  3. 3. Implement parameterized queries (prepared statements) in /login.php for the User parameter to remediate the SQL injection.
  4. 4. Replace the current login logic with: Use prepared statements like $stmt = $conn->prepare('SELECT * FROM users WHERE username = ?'); $stmt->bind_param('s', $username);
  5. 5. Apply input validation and output encoding for all user inputs.
  6. 6. Consider migrating to a maintained note-sharing platform with active security support.
Caveat No upgrade path available - this is an educational project with no official security patches or maintained versions

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

Fix this in Online Notes Sharing Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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