CVE-2024-48781
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 · uneditedAn issue in Wanxing Technology Yitu Project Management Kirin Edition 2.3.6 allows a remote attacker to execute arbitrary code via a specially constructed so file/opt/EdrawProj-2/plugins/imageformat.
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 confidenceArbitrary file upload vulnerability in Wanxing Technology Yitu Project Management Kirin Edition 2.3.6 allows remote attackers to upload malicious shared object (.so) files to the /opt/EdrawProj-2/plugins/imageformat directory, enabling remote code execution with the privileges of the running application.
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
- 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.
-
Identify if Yitu Project Management Kirin Edition is installedCheck for the application binary or installation directory. Common locations: /opt/EdrawProj-, /usr/local/EdrawProj, or check system package manager for the product.Affected if The application is found at any installation path and version is 2.3.6 or if version cannot be determined but the product is present.
-
Verify the vulnerable plugin directory existsInspect the path /opt/EdrawProj-2/plugins/imageformat/ for existence. Use command: ls -la /opt/EdrawProj-2/plugins/imageformat/ 2>/dev/null or similar for your installation path.Affected if The directory /opt/EdrawProj-2/plugins/imageformat/ exists and is writable by the application process.
-
Enumerate shared object files in the plugin directoryList all .so files in the imageformat plugin directory: find /opt/EdrawProj-2/plugins/imageformat/ -name "*.so" -type fAffected if Any .so files are present that were not installed by the vendor or that are unexpected.
-
Check file modification timestamps on the plugin directoryReview recent file changes: stat /opt/EdrawProj-2/plugins/imageformat/ and logon/audit logs for modifications to this path.Affected if The directory or contained .so files show modification timestamps inconsistent with known legitimate updates.
-
Determine if the service is network accessible without authenticationVerify network binding configuration. Check if the application listens on a network interface (0.0.0.0) and does not require authentication for plugin upload functionality.Affected if The application is exposed to unauthenticated network access and the imageformat plugin directory is writable.
A system is affected if Yitu Project Management Kirin Edition version 2.3.6 is installed, the /opt/EdrawProj-2/plugins/imageformat/ directory exists and is writable, and the service is network-accessible to unauthenticated attackers.
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 dataRestrict file upload functionality to validate file types and prevent .so files in plugin directories; implement strict allowlist validation and proper file permission controls on the plugins folder.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48781 — 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-2024-48781 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