CVE-2023-1741
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 · uneditedA vulnerability was found in jeecg-boot 3.5.0. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file SysDictMapper.java of the component Sleep Command Handler. The manipulation leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-224629 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 · moderate confidenceSQL injection vulnerability in jeecg-boot 3.5.0's SysDictMapper.java component, specifically in the Sleep Command Handler functionality. The vulnerability allows remote attackers to inject malicious SQL queries via unsanitized input. The public disclosure of the exploit increases the likelihood of active exploitation.
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= 3.5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the installed jeecg-boot versionCheck your application or dependency management system for the exact jeecg-boot version. Common ways: check pom.xml for jeecg-boot version, check the WAR/JAR file manifest, or query the application's version endpoint if available.Affected if The installed version is exactly 3.5.0
-
Locate SysDictMapper.java in the codebaseSearch your codebase for the file SysDictMapper.java. This is typically found in the mapper layer, often under a path like src/main/java/org/jeecg/modules/system/mapper/ or similar mapper package structure.Affected if The file SysDictMapper.java exists in the application and the version is 3.5.0
-
Inspect the Sleep Command Handler implementationOpen SysDictMapper.java and search for any method or handler related to 'Sleep' command. Review how user input is processed in that handler.Affected if A Sleep Command Handler exists that processes unsanitized input from the SQL mapping layer
-
Check API endpoints exposing dict functionalityReview your application's REST API endpoints that invoke the SysDictMapper, particularly any endpoints that accept command parameters passed to dict queries.Affected if Endpoints exist that pass user-supplied parameters to dict mapper queries without proper sanitization
If the jeecg-boot version is exactly 3.5.0 and the SysDictMapper with Sleep Command Handler is present and accessible via API, the environment is affected by CVE-2023-1741.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of jeecg-boot if available, or implement proper input validation and parameterized queries in SysDictMapper.java to remediate the SQL injection. Conduct a full code audit for similar injection points.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1741 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-1741 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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