dbcve.org
Society Management SystemApplication · Angeljudesuarez

CVE-2026-1119

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-18
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. The affected element is an unknown function of the file /admin/delete_activity.php. Executing a manipulation of the argument activity_id can lead to sql injection. It is possible to launch 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

SQL injection vulnerability in itsourcecode Society Management System 1.0 allows remote attackers to inject malicious SQL code via the activity_id parameter in /admin/delete_activity.php. The lack of input sanitization or parameterized queries in the delete_activity functionality enables unauthenticated attackers to manipulate database queries.

MitigationImplement prepared statements/parameterized queries for all database operations in delete_activity.php, or at minimum sanitize and validate the activity_id parameter using whitelist validation before using it in SQL queries.

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. Identify if Society Management System is installed
    Check your web server for the presence of the Society Management System application directory. Look for files matching 'society' or 'management' in your web root. Check application inventory or installed software lists for 'Angeljudesuarez Society Management System' or 'itsourcecode Society Management System' version 1.0.
    Affected if The application is installed and the version is 1.0
  2. Locate the vulnerable PHP file
    Search for the file /admin/delete_activity.php in your web root where the application is deployed. Use file system search or check the application directory structure for this specific file.
    Affected if The file delete_activity.php exists in the /admin/ directory of the application
  3. Verify the application is network-accessible
    Confirm the application's /admin/ endpoint is reachable over the network. Test HTTP/HTTPS access to yourserver/[path-to-app]/admin/ without providing authentication credentials.
    Affected if The /admin/ directory is accessible without authentication (no login required to reach it)
  4. Examine the vulnerable code in delete_activity.php
    Open delete_activity.php and locate the SQL query that uses the activity_id parameter. Check if the parameter is directly concatenated into the SQL query without using prepared statements or parameter binding.
    Affected if The activity_id parameter is used in a SQL query without parameterized queries or input sanitization

Your environment is affected if you have Angeljudesuarez Society Management System version 1.0 installed with the /admin/delete_activity.php file accessible and the activity_id parameter handled without parameterized queries.

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/parameterized queries for all database operations in delete_activity.php, or at minimum sanitize and validate the activity_id parameter using whitelist validation before using it in SQL queries.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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