Skip to content

CWE-943: Improper Neutralization of Special Elements in Data Query Logic

Class

The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.

Depending on the capabilities of the query language, an attacker could inject additional logic into the query to: Modify the intended selection criteria, thus changing which data entities (e.g., records) are returned, modified, or otherwise manipulated Append additional commands to the query Return more entities than intended Return fewer entities than intended Cause entities to be sorted in an unexpected way The ability to execute additional commands or change which entities are returned has obvious risks. But when the product logic depends on the order or number of entities, this can also lead to vulnerabilities. For example, if the query expects to return only one entity that specifies an administrative user, but an attacker can change which entities are returned, this could cause the logic to return information for a regular user and incorrectly assume that the user has administrative privileges. While this weakness is most commonly associated with SQL injection, there are many other query languages that are also subject to injection attacks, including HTSQL, LDAP, DQL, XQuery, Xpath, and "NoSQL" languages.

Consequences

  • Confidentiality, Integrity, Availability, Access Control: Bypass Protection Mechanism, Read Application Data, Modify Application Data, Varies by Context

Recent advisories

  • GHSA-v6q3-xqxm-6f5v — Ghost: Invite Token Disclosure in Ghost Admin API
  • GHSA-53vv-xm9f-mm82 — Ghost: Password Hash Ordering Disclosure in Ghost Admin API
  • GHSA-6q6j-f24j-p477 — Ghost: Authorization Bypass in Comments Feature
  • GHSA-qrh6-cwg3-343x — Ghost: Authorization Bypass in Comment Like Feature
  • EEF-CVE-2026-78691 — Unescaped backslash allows LIKE wildcard injection in AshSql string search
  • EEF-CVE-2026-70395 — Predicate injection in manage_relationship belongs_to lookup discloses secret lookup keys in Ash
  • GHSA-pmpg-2mxq-6xwr — Budibase: NoSQL injection in MongoDB integration: collection dump, $where JS exec, cross-collection pivot, arbitrary update/delete
  • GHSA-qw6m-8fw2-2v64 — Budibase: NoSQL Injection via JSON Parameter Interpolation in MongoDB Query Execution
  • GHSA-wf65-4jjx-q444 — PraisonAI: PGVector and Cassandra knowledge stores interpolate vector dimensions into DDL
  • GHSA-8qv3-p479-cj62 — Budibase has nonymous NoSQL operator injection via published-app query templates
  • GHSA-p5cp-r7rg-qpxc — Open WebUI: RAG ACL Bypass in Milvus Multitenancy Mode
  • GHSA-5pv2-86qj-5jf9 — Cockpit has NoSQL Injection Through Content Aggregation Pipelines
  • GHSA-28g4-38q8-3cwc — Flowise: Cypher Injection in GraphCypherQAChain
  • GHSA-gcp9-5jc8-976x — phpMyFAQ has a LIKE Wildcard Injection in Search.php — Unescaped % and _ Metacharacters Enable Broad Content Disclosure
  • GHSA-5fw2-8jcv-xh87 — Parse Server: Account takeover via operator injection in authentication data identifier

All advisories for CWE-943

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor