Apartment Management SystemApplication · Admerc

CVE-2025-9645

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-29
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 identified in itsourcecode Apartment Management System 1.0. This affects an unknown part of the file /t_dashboard/r_all_info.php. The manipulation of the argument mid leads to sql injection. The attack can be initiated remotely. The exploit is publicly available and might 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 critical SQL injection vulnerability exists in itsourcecode Apartment Management System 1.0. The vulnerability is located in /t_dashboard/r_all_info.php where the 'mid' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL commands.

MitigationImplement parameterized queries (prepared statements) to sanitize the 'mid' parameter before using it in SQL queries. If vendor patch unavailable, deploy a WAF as a temporary mitigation.

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
Apartment 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 product installation
    Locate the itsourcecode Apartment Management System installation directory. Common paths include /var/www/html/, C:\inetpub\wwwroot\, or within the web server's document root. Look for application files matching this system.
    Affected if The system is installed and running
  2. Verify installed version
    Check the application's version information. This may be in a README file, a version config file, or the application itself. Compare against the affected version: 1.0
    Affected if The installed version is exactly 1.0 (Admerc Apartment Management System)
  3. Locate vulnerable script
    Check for the presence of the file /t_dashboard/r_all_info.php within the application's web directory. This file handles the 'mid' parameter.
    Affected if The file /t_dashboard/r_all_info.php exists in the installation
  4. Identify application accessibility
    Verify the web application is accessible and the vulnerable endpoint responds. Attempt to access the URL path /t_dashboard/r_all_info.php via HTTP/HTTPS request.
    Affected if The endpoint /t_dashboard/r_all_info.php is accessible and responds to requests
  5. Check input handling on mid parameter
    Review the source code of r_all_info.php to confirm the 'mid' parameter is processed without sanitization or parameterized queries. Look for direct inclusion of the parameter in SQL statements.
    Affected if The 'mid' parameter is used in SQL queries without prepared statements or input validation

A user is affected if they run Admerc Apartment Management System version 1.0 with the accessible file /t_dashboard/r_all_info.php that processes the 'mid' parameter without SQL parameterization.

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 parameterized queries (prepared statements) to sanitize the 'mid' parameter before using it in SQL queries. If vendor patch unavailable, deploy a WAF as a temporary mitigation.

Fix this in Apartment Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-9645 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