CVE-2026-114374 — leomoon-studios wiki-go fetch-metadata Endpoint metadata_api.go server-side request forgery
A vulnerability was identified in leomoon-studios wiki-go up to 1.9.1. This impacts an unknown function of the file internal/handlers/metadata_api.go of the component fetch-metadata Endpoint. Such manipulation leads to server-side request forgery. It is possible to launch the attack remotely. The exploit is publicly available and might be used. Upgrading to version 1.9.2 will fix this issue. The name of the patch is 25498ebf5c012b870967e38eec2a1e5133fa1a83. Upgrading the affected component is recommended.
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
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+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.
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 (Leomoon-studios Wiki-go).
- 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.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Leomoon-studios | Wiki-go | version 1.9.0version 1.9.1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
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 |
|---|---|---|---|---|---|
| 5.3 | CVSS 4.0 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 2.1 | CVSS 4.0 | Low | — | — | cna@vuldb.com via NIST National Vulnerability Database |
| 4.3 | CVSS 3.1 | Medium | 2.8 | 1.4 | cna@vuldb.com via NIST National Vulnerability Database |
| 4.3 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 4.3 | CVSS 3.1 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 4.3 | CVSS 3.0 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 4.0 | CVSS 2.0 | Medium | 8.0 | 2.9 | cna@vuldb.com via NIST National Vulnerability Database |
| 4.0 | CVSS 2.0 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (score shown at the top: cna@vuldb.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 22, 2026 → Oct 27, 2026 · 6 reading(s) · max 0.24%
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
- Source status changed · Received → Deferred
- Affected products added · leomoon-studios/wiki-go
- Record published
- CVSS changed · 4.3
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 21, 2026 – Oct 22, 2026
- 1× Official description updated · Oct 21, 2026 – Oct 21, 2026
References
11 on the record
- github.com/leomoon-studios/wiki-go/commit/25498ebf5c012b870967e38eec2a1e5133fa1a
- github.com/leomoon-studios/wiki-go/releases/tag/v1.9.2
- nvd.nist.gov/vuln/detail/CVE-2026-114374
- github.com/leomoon-studios/wiki-go/security/advisories/GHSA-7q4p-98g4-pwp7
- github.com/advisories/GHSA-p8fx-449f-qx64
- vuldb.com/cve/CVE-2026-114374
- vuldb.com/vuln/424731/cti
- github.com/leomoon-studios/wiki-go
- github.com/leomoon-studios/wiki-go/
- vuldb.com/vuln/424731
- vuldb.com/submit/1019388
Elsewhere on this site
Related CVEs (same products)
- Low CVE-2026-114377 leomoon-studios wiki-go Comment Deletion comments.go DeleteComment path traversal 6d
- Medium CVE-2026-114375 leomoon-studios wiki-go Files Rename API files.go RenameFileHandler path traversal 6d
- Medium CVE-2026-114376 leomoon-studios wiki-go API editor.go SourceHandler path traversal 6d
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 CISA SSVC assessment.
- 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-114374 is "leomoon-studios wiki-go fetch-metadata Endpoint metadata_api.go server-side request forgery", rated Medium. It affects Wiki-go (Leomoon-studios); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.3 describes technical severity. EPSS 0.24% 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.