Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

SQL injection in Imaster MEMS Events CRM /memsdemo/login.php (phone parameter)

IdentifiersCVE-2025-41006CWE-89· Improper Neutralization of Special…

Imaster’s MEMS Events CRM is vulnerable to SQL injection via the ‘phone’ parameter handled by the ‘/memsdemo/login.php’ endpoint. The application improperly neutralizes special elements used in SQL commands (CWE-89), allowing attacker-controlled input in the ‘phone’ field to be incorporated into backend database queries, enabling execution of unintended SQL statements.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote exploitation can allow SQL injection against the backend database, potentially resulting in unauthorized read/write access to data, data exfiltration, and modification of records. Depending on the query context in the login flow, exploitation may also enable authentication bypass. The published CVSS v4.0 base score is 9.3 (Critical) with AV:N/AC:L/AT:N/PR:N/UI:N and high impacts to confidentiality, integrity, and availability (VC:H/VI:H/VA:H).

Mitigation

If you can’t patch tonight, do this now.

Until a vendor fix is available, enforce strict server-side validation for the ‘phone’ parameter (allowlist expected phone formats), and ensure all database access uses prepared statements. Deploy WAF rules to detect/block SQLi payloads targeting ‘/memsdemo/login.php’ (e.g., SQL metacharacters/keywords in ‘phone’). If feasible, restrict access to the affected endpoint (IP allowlisting/VPN) and increase monitoring/logging for SQLi attempts.

Remediation

Patch, then assume compromise.

Apply a vendor-provided fixed release when available. Refactor ‘/memsdemo/login.php’ to use parameterized queries/prepared statements (eliminate string concatenation for SQL construction), and validate/filter inputs sent to the database. Ensure the web application’s database account uses least-privilege permissions to reduce blast radius if injection occurs.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ImasterMems Events Crmapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.