dbcve.org
E Invoice Approval SystemApplication · Infodrom

CVE-2023-35066

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-25
Fix available
A fix is available. Upgrade to 20230701 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Infodrom Software E-Invoice Approval System allows SQL Injection. This issue affects E-Invoice Approval System: before v.20230701.

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 Infodrom Software E-Invoice Approval System allows attackers to inject malicious SQL commands via unsanitized user input, potentially enabling unauthorized data access, modification, or deletion of database contents.

MitigationUpdate E-Invoice Approval System to version 20230701 or later to apply vendor-provided patches addressing the SQL injection vulnerability.

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
E Invoice Approval SystemApplication
Affected:< 20230701

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 if Infodrom E-Invoice Approval System is deployed
    Locate the E-Invoice Approval System installation in your environment. This is typically a web application server (such as IIS, Apache, or Tomcat) running the Infodrom E-Invoice application. Check your application inventory or web server configurations for the presence of this specific product.
    Affected if The system is present in your environment and you cannot confirm it is version 20230701 or later.
  2. Determine the installed version of E-Invoice Approval System
    Locate the version information for your installation. This may be found in: the application's about page or help menu, a version.txt or VERSION file within the application directory, the application configuration files (such as web.config, application.properties, or similar), or the software's administrative interface. Compare your found version against the build date or version number.
    Affected if The version is earlier than the 20230701 build (or the version cannot be verified).
  3. Verify the application handles user-supplied input
    Examine the application's input handling. SQL injection vulnerabilities require that user-controlled data reaches database queries. Review web application firewall (WAF) logs, application logs, or traffic logs for the E-Invoice Approval System to confirm it processes user input in fields such as login forms, search parameters, invoice search, or approval workflows.
    Affected if The application accepts user input and you are running a version earlier than 20230701, the vulnerability is likely present and exploitable.

You are affected if Infodrom E-Invoice Approval System is installed and the version is earlier than 20230701, regardless of whether user input fields are actively used.

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

Update E-Invoice Approval System to version 20230701 or later to apply vendor-provided patches addressing the SQL injection vulnerability.

Recommended fix Moderate confidence

20230701

  1. 1. Backup the current E-Invoice Approval System database and configuration files.
  2. 2. Verify the current installed version of E-Invoice Approval System.
  3. 3. Obtain the updated version (20230701) from the official vendor Infodrom Software.
  4. 4. Stop the E-Invoice Approval System services.
  5. 5. Install the updated version 20230701 following vendor documentation.
  6. 6. Verify the upgrade was successful by checking the application version.
  7. 7. Test the application functionality to ensure proper operation.
  8. 8. Verify the SQL injection vulnerability is resolved by confirming the patch is applied.
Caveat Review release notes for any configuration or database schema changes that may require adjustment

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

Fix this in E Invoice Approval System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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