dbcve.org
Society Management SystemApplication · Angeljudesuarez

CVE-2025-15353

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 vulnerability was detected in itsourcecode Society Management System 1.0. Impacted is the function edit_admin_query of the file /admin/edit_admin_query.php. Performing manipulation of the argument Username results in sql injection. It is possible to initiate the attack remotely. The exploit is now 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 itsourcecode Society Management System 1.0's admin panel. The edit_admin_query.php file fails to properly sanitize the Username parameter before using it in database queries, allowing remote attackers to inject malicious SQL commands.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the Username parameter in edit_admin_query.php, and implement proper input validation. Apply the fix immediately given the critical CVSS score and public exploit availability.

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. Locate the vulnerable PHP file
    Search the web root for edit_admin_query.php using: find /var/www -name 'edit_admin_query.php' 2>/dev/null (Windows: dir /s /b edit_admin_query.php)
    Affected if The file edit_admin_query.php exists in the application directory and the software version is 1.0
  2. Identify the software version
    Check for version indicators in source files, README, or meta tags. Common paths include version.php, about.php, or the main index page source.
    Affected if The installed version is Society Management System 1.0 (or Angeljudesuarez Society Management System 1.0)
  3. Inspect the vulnerable code pattern
    Open edit_admin_query.php and examine how the Username parameter is handled. Look for direct insertion of $_POST or $_GET['Username'] into SQL queries without escaping, parameterized queries, or validation functions.
    Affected if The Username parameter is used directly in SQL queries without prepared statements, escaping, or input validation functions such as mysqli_real_escape_string or htmlspecialchars with SQL-aware filtering
  4. Verify admin panel accessibility
    Check if the admin panel is accessible by navigating to the typical admin path (often /admin, /adminpanel, or /admin/login.php) and locate edit_admin.php or edit_admin_query.php
    Affected if The admin panel and edit_admin_query.php are accessible without additional authentication barriers or the application uses default credentials
  5. Check for the vulnerable parameter in HTTP requests
    Review application logs or capture a request to edit_admin_query.php and inspect whether the Username parameter is submitted without sanitization in the request body.
    Affected if The Username parameter accepts special SQL characters (quotes, semicolons, UNION, etc.) without being filtered or rejected

You are affected if you run Society Management System version 1.0 and the edit_admin_query.php file contains unsanitized Username parameter usage in SQL 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

Replace dynamic SQL queries with parameterized queries/prepared statements for the Username parameter in edit_admin_query.php, and implement proper input validation. Apply the fix immediately given the critical CVSS score and public exploit availability.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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