dbcve.org
MispApplication · Misp Project

CVE-2026-44381

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 2.5.37 or later.
See remediation →
62/100
Remediation priority · Elevated
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
MISP is an open source threat intelligence and sharing platform. Prior to 2.5.37, a SQL injection vulnerability existed in the handling of user-controlled ordering parameters in the event and shadow attribute listing endpoints. The affected code accepted order or sort values from request parameters and incorporated them into database query ordering clauses without sufficient validation of the requested field name. An attacker with access to the affected endpoints could craft a malicious ordering parameter to manipulate the generated SQL query. Depending on database permissions and query context, this could potentially allow unauthorized access to data, modification of query behavior, or other database-level impact. This vulnerability is fixed in 2.5.37.

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 MISP prior to 2.5.37 where user-controlled ordering parameters (order/sort) from request inputs are incorporated into SQL ORDER BY clauses without proper field name validation. Attackers with access to event or shadow attribute listing endpoints can craft malicious ordering parameter values to manipulate query behavior.

MitigationUpgrade MISP to version 2.5.37 or later which includes proper validation of ordering parameter field names before use in SQL queries.

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
MispApplication
Affected:< 2.5.37

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 installed MISP version
    Locate the MISP version file or admin interface - typically found in /var/www/MISP/VERSION or through the MISP web interface under Administration > Server Settings > MISP settings. Compare the version number to 2.5.37.
    Affected if The installed version is lower than 2.5.37
  2. Confirm access to event listing endpoint
    Verify that the account being tested has permission to access the event index/list view. Log in and navigate to the events page or use the /events/index API endpoint.
    Affected if User has access to the event listing endpoint and can submit request parameters
  3. Confirm access to shadow attribute listing endpoint
    Verify that the account has permission to access shadow attribute (proposal) listings. This is typically found under the 'Proposals' section or via /shadow_attributes/index API endpoint.
    Affected if User has access to shadow attribute listing and can submit request parameters
  4. Test ordering parameter acceptance
    Submit a request to the event or shadow attribute listing endpoint with an 'order' or 'sort' parameter in the request (either GET or POST). For example: /events/index?order=somefield or /events/index?sort=fieldname. Observe if the parameter is accepted and affects query results.
    Affected if The application accepts and processes custom values in the order/sort parameters without rejecting unknown field names

A user is affected if their MISP installation is version 2.5.36 or earlier AND they have access to event or shadow attribute listing endpoints where the order/sort parameter can be controlled.

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.

dbcve · scoped
Upgrade available Upgrade to 2.5.37 or later
Fixed in 2.5.37
Interim mitigation

Upgrade MISP to version 2.5.37 or later which includes proper validation of ordering parameter field names before use in SQL queries.

Recommended fix High confidence

MISP 2.5.37

  1. Download and install MISP version 2.5.37 or later from the official MISP GitHub repository (github.com/MISP/MISP)
  2. Verify the upgrade was successful by checking the MISP version in the web interface under Administration -> Server Settings -> MISP settings -> version
  3. Test that the event and shadow attribute listing endpoints function correctly with various sorting parameters to confirm the vulnerability is patched

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Misp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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