dbcve.org
JfinaloaApplication · Jfinaloa Project

CVE-2023-0758

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A vulnerability was found in glorylion JFinalOA 1.0.2 and classified as critical. This issue affects some unknown processing of the file src/main/java/com/pointlion/mvc/common/model/SysOrg.java. The manipulation of the argument id leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-220469 was assigned to this vulnerability.

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 glorylion JFinalOA 1.0.2 allows remote attackers to inject malicious SQL queries through the 'id' parameter in the SysOrg.java component. The vulnerability has a critical CVSS score of 9.8 due to the ease of exploitation and potential for complete system compromise. A public exploit is available, increasing urgency for remediation.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in SysOrg.java, implement strict input validation on the 'id' parameter, and conduct a comprehensive code review to identify and remediate similar injection points throughout the application.

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
JfinaloaApplication
Affected:= 1.0.2

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 JFinalOA installation
    Locate the JFinalOA application deployment (war file or extracted directory) and check the version information in the application manifest, README, or version configuration file.
    Affected if The installed version is JFinalOA 1.0.2 exactly.
  2. Locate SysOrg.java component
    Search the application source code or decompiled classes for the SysOrg.java file, typically found in the source tree under controllers or similar package directories.
    Affected if The SysOrg.java file exists in the application codebase.
  3. Verify vulnerable parameter handling
    Examine the SysOrg.java source code and look for SQL query construction that uses the 'id' parameter directly in dynamic SQL statements without parameterization.
    Affected if The 'id' parameter is used in SQL queries without prepared statements or parameter binding.
  4. Check application accessibility
    Determine if the endpoint handled by SysOrg.java is exposed via the web application. Identify the URL path and HTTP methods (GET/POST) that invoke the vulnerable code.
    Affected if The vulnerable endpoint is accessible over the network without authentication or with obtainable credentials.
  5. Review database configuration
    Inspect the application configuration files (such as database connection settings) to confirm the application connects to a database that could be compromised via SQL injection.
    Affected if The application uses a database that would be reachable through the injection point.

You are affected if you are running JFinalOA version 1.0.2 with the SysOrg.java component and the 'id' parameter is used in unsanitized SQL queries within that component.

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 in SysOrg.java, implement strict input validation on the 'id' parameter, and conduct a comprehensive code review to identify and remediate similar injection points throughout the application.

Fix this in Jfinaloa Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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