dbcve.org
Society Management SystemApplication · Angeljudesuarez

CVE-2026-2115

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-07
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 flaw has been found in itsourcecode Society Management System 1.0. This issue affects some unknown processing of the file /admin/delete_expenses.php. This manipulation of the argument expenses_id causes sql injection. It is possible to initiate the attack remotely. The exploit has been published 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

A SQL injection vulnerability exists in the itsourcecode Society Management System 1.0 at the /admin/delete_expenses.php endpoint. The expenses_id parameter is not properly sanitized before being used in database queries, allowing remote attackers to inject arbitrary SQL commands.

MitigationImplement prepared statements or parameterized queries for the expenses_id parameter, or apply proper input validation and escaping. Restrict database privileges to the minimum required for 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
Society Management 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. Confirm Society Management System is installed
    Check for the presence of the application by looking for directories or files related to 'Society Management System' or 'itsourcecode' on the web server. Also check HTTP responses for titles or strings containing 'Society Management System' when accessing the application.
    Affected if The application is found to be running on the system
  2. Verify the installed version is 1.0
    Look for version information in the application. Check common locations like README files, footer text on pages, or meta tags in HTML source. Compare the found version against the affected range (= 1.0).
    Affected if The installed version is exactly 1.0
  3. Confirm the vulnerable endpoint exists
    Check if the file /admin/delete_expenses.php exists on the web server. Attempt to access it via HTTP request and verify the file is present and returns a response.
    Affected if The file /admin/delete_expenses.php is accessible on the server
  4. Verify the application is reachable over the network
    Confirm the web application is accessible via HTTP/HTTPS from a remote location. Check if the /admin/ directory is reachable and not blocked by authentication or network filters.
    Affected if The application and its /admin/ endpoints are network-accessible
  5. Test if expenses_id parameter is processed without sanitization
    Send a test request to /admin/delete_expenses.php with an expenses_id value and observe the application's response. The vulnerability exists if the parameter appears to be used directly in a SQL query without visible sanitization or prepared statements.
    Affected if The expenses_id parameter is processed without proper sanitization or parameterized queries

A user is affected if they are running Society Management System version 1.0 with the /admin/delete_expenses.php endpoint accessible and the expenses_id parameter being used in SQL queries without sanitization.

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 prepared statements or parameterized queries for the expenses_id parameter, or apply proper input validation and escaping. Restrict database privileges to the minimum required for the application.

Fix this in Society Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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