dbcve.org
RiswebApplication · Ebmtech

CVE-2024-26264

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-15
Fix available
A fix is available. Upgrade to 3.0 or later.
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
EBM Technologies RISWEB's specific query function parameter does not properly restrict user input, and this feature page is accessible without login. This allows remote attackers to inject SQL commands without authentication, enabling them to read, modify, and delete database records.

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

Critical SQL injection vulnerability in EBM Technologies RISWEB's query function where user input is not properly restricted. The affected feature page is accessible without authentication, allowing remote attackers to inject arbitrary SQL commands and potentially read, modify, or delete database records.

MitigationImmediately restrict access to the vulnerable query function page by requiring authentication, and implement parameterized queries or prepared statements to prevent SQL injection. If a patch is available from the vendor, apply it as soon as possible.

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
RiswebApplication
Affected:>= 1.0, < 3.0

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
High
Integrity
High
Availability
High

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

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 RISWEB installation
    Locate the EBM Technologies RISWEB application in your environment. Check web server directories, application deployment folders, or system inventory records for RISWEB components. Look for files named risweb, ebm, or related web application archives.
    Affected if RISWEB is installed on the system and the application files are found in web-accessible directories.
  2. Determine installed version
    Locate version information within the RISWEB installation. Check configuration files (such as config.xml, version.properties, or web.xml), about pages, or the application's footer for a version number. Compare your found version against the affected range of >=1.0 and <3.0.
    Affected if The installed version falls within >=1.0 and <3.0, indicating the system is potentially vulnerable.
  3. Locate the query function page
    Identify the query function endpoint within the RISWEB web application. Common paths may include /query, /search, /risquery, or similar. Check the application's sitemap, navigation structure, or web.xml routing configuration for the query functionality.
    Affected if The query function page exists within the RISWEB application structure.
  4. Verify unauthenticated access
    Attempt to access the identified query function URL without providing any authentication credentials (cookies, tokens, or login). Use a web browser or HTTP client to make an unauthenticated GET request to the query page endpoint.
    Affected if The query function page loads or responds without requiring authentication, indicating the vulnerability is exploitable.
  5. Test for SQL injection
    Submit SQL special characters or typical injection payloads (such as single quotes, UNION SELECT, or time-based sleep commands) in the query function's input parameters. Observe if the application returns database errors, unexpected data, or exhibits unusual response delays.
    Affected if The application returns SQL error messages, displays unexpected database content, or responds to injection payloads in ways that indicate direct SQL query execution.

If RISWEB version 1.0 or higher but below 3.0 is installed and the query function page is accessible without authentication, the environment is affected by this SQL injection vulnerability.

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 3.0 or later
Fixed in 3.0
Interim mitigation

Immediately restrict access to the vulnerable query function page by requiring authentication, and implement parameterized queries or prepared statements to prevent SQL injection. If a patch is available from the vendor, apply it as soon as possible.

Recommended fix Moderate confidence

Version 3.0 or latest stable release from EBM Technologies

  1. 1. Identify the current installed version of Risweb by checking the application configuration or contacting system administrator
  2. 2. Contact EBM Technologies to obtain the latest stable version (version 3.0 or later) which contains the security fix
  3. 3. Before upgrading, perform a complete backup of the database and application configuration
  4. 4. Test the upgrade in a non-production environment to verify compatibility
  5. 5. Schedule a maintenance window for the production upgrade
  6. 6. Apply the upgrade to version 3.0 or the latest available secure release
  7. 7. After upgrade, verify that the SQL injection vulnerability is resolved by testing the specific query function
  8. 8. Confirm normal application functionality after the upgrade
Caveat Review release notes from EBM Technologies for any breaking changes between your current version and version 3.0; custom integrations or configurations may need adjustment

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

Fix this in Risweb Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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