CVE-2025-9406
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 weakness has been identified in xuhuisheng lemon up to 1.13.0. This affects the function uploadImage of the file CmsArticleController.java of the component com.mossle.cms.web.CmsArticleController.uploadImage. This manipulation of the argument Upload causes unrestricted upload. The attack can be initiated remotely. The exploit has been made available to the public and could be exploited.
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 confidenceUnrestricted file upload vulnerability in the CmsArticleController.uploadImage function of xuhuisheng lemon CMS (versions up to 1.13.0). The function fails to properly validate the Upload argument, allowing remote attackers to upload arbitrary files (potentially malicious executables, webshells, or scripts) without restriction. This could lead to remote code execution if uploaded files are accessible via the web server.
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<= 1.13.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.
-
Identify if lemon CMS is installedCheck your web server for the presence of lemon CMS (also known as xuhuisheng or Mossle Lemon). Look for common installation paths or check your application inventory.Affected if lemon CMS is present on the system
-
Determine the installed versionLocate the version information file or admin panel in the lemon CMS installation. This is typically found in a version file, about page, or admin dashboard.Affected if the installed version is 1.13.0 or lower
-
Verify the upload functionality existsCheck if the CmsArticleController.uploadImage function is present in the codebase. This is typically found in the controller files under the article or upload module.Affected if the uploadImage function exists in the codebase
-
Check upload directory web accessibilityLocate the configured upload directory (commonly 'upload', 'uploads', 'attached', or similar in the webroot) and verify if it is served by the web server.Affected if the upload directory is located inside the webroot and directly accessible via HTTP
-
Inspect upload directory for suspicious filesList all files in the upload directory and check for unexpected extensions such as .php, .asp, .jsp, .exe, .sh, or other executable/script types that were not explicitly allowed.Affected if files with potentially malicious extensions (especially executable or script files) are present in the upload directory
You are affected if lemon CMS (Mossle Lemon) version 1.13.0 or lower is installed, the upload functionality exists, and the upload directory is web-accessible with improperly validated files present.
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 dataImplement strict allowlist-based file validation (checking magic bytes/content-type) before processing uploads; store uploaded files outside the webroot or with non-executable extensions; rename uploaded files to prevent filename-based attacks; ensure authentication and authorization checks are enforced on the upload endpoint.
- 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-2025-9406 — 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-2025-9406 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