dbcve.org
Project Monitoring SystemApplication · Fabian

CVE-2025-11585

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-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 found in code-projects Project Monitoring System 1.0. The impacted element is an unknown function of the file /useredit.php. The manipulation of the argument uid results in sql injection. The attack can be executed remotely. The exploit has been made public and could 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 the Project Monitoring System 1.0 allows remote attackers to inject malicious SQL code via the uid parameter in /useredit.php. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the uid parameter and all user inputs in useredit.php. Apply input validation and output encoding as defense-in-depth measures.

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
Project Monitoring SystemApplication
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 if Fabian Project Monitoring System is installed
    Check for the presence of the application directory. Common paths include /var/www/html/, /www/, or C:\inetpub\wwwroot\ on Windows servers. Look for folders containing 'project monitoring' or 'fabian' in the name.
    Affected if The Fabian Project Monitoring System application directory exists on the server.
  2. Confirm the installed version is 1.0
    Locate version information in the application. Check for a version.php file, about.php, or readme.txt within the application root directory. Alternatively, examine the HTML source of any page for version metadata.
    Affected if The application version is exactly 1.0.
  3. Verify the vulnerable file exists
    Check for the presence of /useredit.php in the web root directory of the application. For example, if the app is at /var/www/html/project-monitoring/, verify /var/www/html/project-monitoring/useredit.php exists.
    Affected if The file useredit.php exists in the application directory.
  4. Check if application database is configured and active
    Examine the application configuration file (often config.php, db.php, or settings.php) to verify database credentials are populated and the application is connecting to a database. Attempt to access the application via HTTP to confirm it is running.
    Affected if The application is configured with database credentials and responds to HTTP requests.
  5. Identify if the uid parameter is accessible
    Access the useredit.php page via HTTP request: http://[target]/useredit.php?uid=1 . Observe if the page processes the uid parameter and returns user information or database-related content.
    Affected if The useredit.php page processes the uid parameter and returns database-driven content.

The system is affected if Fabian Project Monitoring System version 1.0 is installed, the useredit.php file exists, and the application is running with an active database connection that processes the uid parameter.

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 parameterized queries/prepared statements for the uid parameter and all user inputs in useredit.php. Apply input validation and output encoding as defense-in-depth measures.

Fix this in Project Monitoring System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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