dbcve.org
Society Management SystemApplication · Angeljudesuarez

CVE-2025-15354

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-30
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/add_admin.php. Executing manipulation of the argument Username 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 manipulate the Username parameter in /admin/add_admin.php to inject malicious SQL queries, potentially gaining unauthorized access to the database or executing arbitrary commands.

MitigationImplement prepared statements/parameterized queries for all database operations involving user input, particularly the Username parameter in add_admin.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
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 installation
    Locate the web application's document root (commonly /var/www/html, /www, or C:\inetpub\wwwroot on Windows servers) and verify the presence of files indicating the Society Management System, such as index.php, login pages, or admin/ directory.
    Affected if The application is not installed or is a different product.
  2. Verify the vulnerable file exists
    Check for the existence of /admin/add_admin.php within the web application's directory structure. This file is where the Username parameter vulnerability is located.
    Affected if The file /admin/add_admin.php does not exist in the application root.
  3. Confirm the application version
    Inspect application files for version information, typically found in a README file, version.php, or within the main index.php or configuration files. Compare the installed version against the affected version 1.0.
    Affected if The installed version is not 1.0 (versions other than 1.0 may not be affected by this specific CVE).
  4. Check if the admin interface is accessible
    Attempt to access the /admin/add_admin.php endpoint via HTTP/HTTPS request (e.g., using curl or a browser) to determine if the vulnerable parameter is exposed and can receive user input.
    Affected if The /admin/add_admin.php endpoint is not reachable or requires authentication that prevents direct access to the Username parameter.
  5. Verify database connectivity
    Examine the application's configuration files (such as config.php, db.php, or similar) to confirm that the application is configured to connect to a database. SQL injection requires an active database connection to be exploitable.
    Affected if The application is not configured with database credentials or is not connected to a database.

Your environment is affected by this CVE if the Society Management System version 1.0 is installed, the file /admin/add_admin.php exists and is accessible, and the application has an active database connection that the Username parameter can interact with.

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 involving user input, particularly the Username parameter in add_admin.php. Apply input validation and output encoding as defense-in-depth measures.

Fix this in Society Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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