dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-30843

HIGH · 7.6 CVSS v3.1 Published 2025-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in setriosoft bizcalendar-web bizcalendar-web allows SQL Injection.This issue affects bizcalendar-web: from n/a through <= 1.1.0.34.

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 setriosoft bizcalendar-web allows attackers to inject malicious SQL commands through unsanitized input. The flaw affects all versions up to and including 1.1.0.34. Successful exploitation could allow unauthorized database access, data exfiltration, or potential system compromise.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements across all database interactions. Apply input validation and enforce least-privilege database accounts as defense-in-depth measures.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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 bizcalendar-web installation
    Locate the bizcalendar-web application directory or check for the web application in the web server's deployed applications. Look for typical installation paths such as /var/www/bizcalendar-web, C:\inetpub\bizcalendar-web, or within application server directories like Tomcat/webapps or IIS default sites.
    Affected if The application is present in the environment and accessible as a web service.
  2. Identify installed version
    Check for a version file, manifest, or about page within the bizcalendar-web application directory. Common locations include version.txt, MANIFEST.MF, or the application's main configuration file which often displays the version number.
    Affected if The identified version is 1.1.0.34 or any earlier version (versions up to and including 1.1.0.34 are affected).
  3. Verify web interface is accessible
    Attempt to access the bizcalendar-web login page or main endpoint over HTTP/HTTPS using curl, wget, or a browser. Confirm the application responds to web requests.
    Affected if The web interface is exposed and responds to requests, meaning the SQL injection attack surface is reachable.
  4. Check for database connectivity configuration
    Examine the application's configuration files for database connection strings, JDBC configurations, or ORM settings. Look for files such as application.properties, application.yml, web.config, or database connection configuration files.
    Affected if Database credentials and connection parameters are configured, indicating the application can interact with a database.
  5. Inspect application logs for SQL errors
    Review application logs, server logs, or error logs for SQL syntax errors, database exceptions, or unusual query patterns that may indicate SQL injection attempts or successful exploitation.
    Affected if SQL-related errors, unexpected database exceptions, or suspicious query patterns appear in the logs.

The environment is affected if bizcalendar-web is installed with version 1.1.0.34 or earlier and the web application interface is accessible, allowing external input to reach the database interaction layer.

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 or prepared statements across all database interactions. Apply input validation and enforce least-privilege database accounts as defense-in-depth measures.

Have this fixed 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 help mitigating

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-2025-30843 — 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-30843 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