CVE-2026-10581
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 DedeCMS 5.7.88. Affected by this vulnerability is the function base64_decode of the file /plus/download.php?open=1. This manipulation of the argument Link causes server-side request forgery. Remote exploitation of the attack is possible. The exploit has been published and may be used.
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 confidenceServer-side request forgery (SSRF) vulnerability in DedeCMS 5.7.88 allows remote attackers to trick the server into making arbitrary HTTP requests via the base64_decoded 'Link' parameter in /plus/download.php?open=1. The lack of validation on the decoded URL enables attackers to target internal services or external systems.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 DedeCMS installationLook for DedeCMS characteristic files or directories such as /dede/ (admin panel), /include/ core directories, or the presence of DedeCMS-specific PHP files in the web root.Affected if DedeCMS is not installed on the server, the vulnerability does not apply.
-
Identify DedeCMS versionCheck common DedeCMS version files or metadata. Typically found in version constants, a /data/ directory file, or the footer of admin pages. Compare the installed version to 5.7.88.Affected if The installed version is 5.7.88 or an unpatched version where the SSRF flaw exists.
-
Verify /plus/download.php existsAccess or check for the presence of /plus/download.php in the web root. This is the vulnerable script endpoint.Affected if The file does not exist, the specific vulnerable endpoint is not present.
-
Confirm Link parameter is accessibleTest if the download.php script accepts a 'Link' parameter via GET or POST request. The vulnerability lies in base64_decode processing this parameter.Affected if The Link parameter is not accepted or processed by the download.php script, the SSRF attack vector is not available.
The environment is affected if DedeCMS version 5.7.88 (or an unpatched version) is installed, the /plus/download.php file exists, and the Link parameter is processed by that script.
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 validation on the Link parameter before base64 decoding, including allowlist-based URL validation, restrict accessible network ranges, and apply output encoding. Consider upgrading DedeCMS if a patched version is available.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10581 — 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-10581 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