dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-41006

CRITICAL · 9.3 CVSS v4.0 Published 2026-01-12
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
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
Imaster's MEMS Events CRM contains an SQL injection vulnerability in ‘phone’ parameter in ‘/memsdemo/login.php’.

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 · moderate confidence

SQL injection vulnerability in Imaster's MEMS Events CRM allows remote attackers to inject malicious SQL queries through the 'phone' parameter in /memsdemo/login.php, potentially enabling unauthorized database access, data exfiltration, or authentication bypass.

MitigationImplement parameterized queries (prepared statements) for all database operations involving user input, particularly the 'phone' parameter. 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.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 MEMS Events CRM installation
    Search the web server for files or directories containing 'mems', 'crm', or 'imaster' in the document root or application directories. Check for the presence of the /memsdemo/login.php file.
    Affected if The MEMS Events CRM application by Imaster is present on the system, particularly if /memsdemo/login.php exists.
  2. Locate the login.php file
    Inspect the web server document root for the path /memsdemo/login.php. If using a web scanner, enumerate directories for 'memsdemo' or similar naming patterns.
    Affected if The file /memsdemo/login.php is found and accessible via the web server.
  3. Check application version
    Examine version information in the application source code, configuration files, or footer/header templates. Look for version strings in comments, meta tags, or specific MEMS Events CRM version files. Compare against any known affected version ranges.
    Affected if The installed version of MEMS Events CRM matches or falls within the affected version range, or the version cannot be determined.
  4. Inspect the phone parameter handling
    Review the source code of /memsdemo/login.php to see how the 'phone' parameter is handled in database queries. Look for direct string concatenation or lack of prepared statements/parameterized queries when inserting the phone input into SQL statements.
    Affected if The 'phone' parameter is used in SQL queries without parameterized queries, prepared statements, or proper input sanitization.
  5. Test for SQL injection vulnerability
    Send a crafted request to /memsdemo/login.php with the phone parameter containing SQL injection payloads (e.g., single quotes, OR 1=1, UNION-based payloads). Observe if the application returns database errors or behaves differently than expected.
    Affected if The application returns SQL syntax errors, database error messages, or exhibits unexpected behavior when special SQL characters are submitted in the phone parameter.

A system is affected if it runs Imaster's MEMS Events CRM with the /memsdemo/login.php endpoint where the phone parameter is handled in SQL queries without prepared statements.

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) for all database operations involving user input, particularly the 'phone' parameter. Apply input validation and output encoding as defense-in-depth measures.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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