CVE-2026-15530
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 flaw has been found in WuzhiCMS up to 4.1.0. Affected by this vulnerability is the function config/listimage of the file /index.php?m=attachment&f=index&v=upload of the component Attachment API. Executing a manipulation can lead to information disclosure. The attack can be launched remotely. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.
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 confidenceWuzhiCMS versions up to 4.1.0 contain an information disclosure vulnerability in the Attachment API component. The vulnerability exists in the config/listimage function accessed via /index.php?m=attachment&f=index&v=upload, where improper handling of user manipulation allows unauthorized access to sensitive information.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Confirm WuzhiCMS installationLook for the WuzhiCMS index.php in the web root and check for typical WuzhiCMS directories such as /core/, /data/, /app/, and /static/Affected if WuzhiCMS files are present in the web directory
-
Identify WuzhiCMS versionCheck the version.php file typically found in /core/ directory, or look for a version marker in the main index.php or a config fileAffected if The installed version is 4.1.0 or any version below 4.1.0
-
Verify attachment module is enabledCheck if the /app/attachment/ directory exists and contains the index.php controller file for the upload functionalityAffected if The attachment module is present and accessible on the server
-
Test vulnerable endpoint accessSend a GET request to /index.php?m=attachment&f=index&v=upload and observe if the listimage function returns file listings or sensitive information without authenticationAffected if The endpoint returns directory listings, file paths, or other sensitive information without requiring authentication
-
Check for information disclosure in listimageInspect the response from the config/listimage function for exposed file paths, upload directories, or system configuration detailsAffected if The response contains sensitive filesystem information or configuration data that should not be publicly accessible
A user is affected if WuzhiCMS version 4.1.0 or lower is installed with the attachment module accessible and the listimage endpoint exposes sensitive information without authorization.
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 access to the attachment upload functionality and implement proper authorization checks in the listimage function to prevent unauthorized information disclosure. Consider upgrading or patching the CMS once a fix is available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15530 — 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-2026-15530 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