CVE-2026-116205 — YesWiki before 4.7.0 Unauthenticated SSRF via [[|URL]] Raw-Inclusion Syntax
YesWiki before 4.7.0 contains an unauthenticated server-side request forgery vulnerability that allows remote attackers to fetch arbitrary URLs by supplying [[|URL]] wiki syntax to the render handler. Attackers can pass the syntax in the content parameter of the page render handler to reach internal hosts and ports and read their responses.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Public exploit/PoC (nuclei)+4
- EPSS 0.5% (30-day exploitation probability)+7
- Technical severity (medium)+3
- CISA SSVC: exploitation "poc"+5
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Yeswiki Yeswiki).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (ssrf), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.9 | CVSS 4.0 | Medium | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 6.9 | CVSS 4.0 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 5.3 | CVSS 3.1 | Medium | 3.9 | 1.4 | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 5.3 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 5.3 | CVSS 3.1 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (score shown at the top: disclosure@vulncheck.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 26, 2026 → Oct 29, 2026 · 4 reading(s) · max 0.51%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Affected products added · yeswiki/yeswiki
- Record published
- CVSS changed · 5.3
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 25, 2026 – Oct 29, 2026
- 1× Official description updated · Oct 25, 2026 – Oct 25, 2026
References
4 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-116828 YesWiki before 4.7.0 SQL Injection via despam.php INTERVAL operand 3d
- Medium CVE-2026-116827 YesWiki before 4.7.0 SSRF via copyUrlToLocalFile in Bazar CSV Import 3d
- Medium CVE-2026-116826 YesWiki before 4.7.0 Authenticated SSRF via Page Duplication API downloadFile 3d
- Medium CVE-2026-116823 YesWiki before 4.7.0 Reflected XSS via BazarField $_REQUEST Fallback 3d
- Medium CVE-2026-116825 YesWiki from 4.6.2 before 4.7.0 HTTP Signature Replay via ActivityPub Inbox 3d
- Medium CVE-2026-116822 YesWiki before 4.7.0 Template Traversal via BazarListeAction template Parameter 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-116205 is "YesWiki before 4.7.0 Unauthenticated SSRF via [[|URL]] Raw-Inclusion Syntax", rated Medium. It affects Yeswiki (Yeswiki); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 0.51% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.