dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-41005

HIGH · 8.7 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 →
93/100
Remediation priority · Urgent
Remotely reachable 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‘keyword’ parameter in ‘/memsdemo/exchange_offers.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 commands through the 'keyword' parameter in '/memsdemo/exchange_offers.php'. This could enable unauthorized database access, data exfiltration, or modification of backend data.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) for the 'keyword' parameter, implement strict input validation, and ensure database accounts use the principle of least privilege.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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. Confirm Imaster MEMS Events CRM installation
    Locate the application installation directory and identify the product name and version from installation manifests, headers, or the application's main page. Check for directories or files associated with MEMS Events CRM.
    Affected if The product Imaster MEMS Events CRM is installed and the version is within the affected range (if known) or unpatched.
  2. Verify exchange_offers.php exists
    Search for the file /memsdemo/exchange_offers.php in the web root or application directory. Use file system search commands (find, dir) or review the deployed file structure.
    Affected if The file /memsdemo/exchange_offers.php exists in the deployment.
  3. Inspect keyword parameter handling
    Review the source code of exchange_offers.php and locate the handling of the 'keyword' parameter. Check if user input is directly concatenated into SQL queries without using parameterized queries (prepared statements) or proper escaping.
    Affected if The 'keyword' parameter is used in dynamic SQL queries without parameterized query implementation.
  4. Check application network exposure
    Verify if the MEMS Events CRM application is accessible over the network. Test connectivity to the /memsdemo/exchange_offers.php endpoint from external locations or confirm the application listens on network interfaces beyond localhost.
    Affected if The application is network-accessible and the vulnerable endpoint can be reached remotely.

You are affected if Imaster MEMS Events CRM is installed with the vulnerable /memsdemo/exchange_offers.php file, and the 'keyword' parameter handling uses dynamic SQL queries instead of parameterized queries, especially if the endpoint is network-accessible.

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 'keyword' parameter, implement strict input validation, and ensure database accounts use the principle of least privilege.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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