CVE Intelligence
Medium SSRF

CVE-2026-116827 — YesWiki before 4.7.0 SSRF via copyUrlToLocalFile in Bazar CSV Import

YesWiki before 4.7.0 contains a server-side request forgery vulnerability in the Bazar CSV import copyUrlToLocalFile() function that allows authenticated administrators to make arbitrary outbound requests by supplying crafted URLs in CSV file or image fields. Attackers can bypass the extension check with a query-string suffix or redirects to fetch cloud metadata credentials, internal services, or local files via file://, with responses stored in the web-accessible files/ directory.

Published Oct 26, 2026 · Updated Oct 26, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+4
  • 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.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.35%
ahead of 28% of scored CVEs · Oct 29, 2026
Affects
Yeswiki
Yeswiki
CVSS base
6.8
Medium · 2 source(s)

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.

  1. Identify exposed assets running the affected vendor/product/version combinations (Yeswiki Yeswiki).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. 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.

VendorProductVersionsStatusSource
Yeswiki Yeswiki < 4.7.0 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.2 CVSS 4.0 High — — disclosure@vulncheck.com via NIST National Vulnerability Database
8.2 CVSS 4.0 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
6.8 CVSS 3.1 Medium 2.3 4.0 disclosure@vulncheck.com via NIST National Vulnerability Database
6.8 CVSS 3.1 Medium — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-918 · Server-Side Request Forgery (SSRF)

Other CVEs with this weakness →

EPSS over time FIRST

Oct 27, 2026 → Oct 29, 2026 · 3 reading(s) · max 0.35%

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.
web/proxy/WAF logsnetwork IDS/IPSegress traffic

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · yeswiki/yeswiki
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 26, 2026
  • CVSS changed · 6.8
    Oct 26, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 26, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 26, 2026 · Alertas do Telegram
  • CVE published
    Oct 26, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 26, 2026 – Oct 26, 2026
  • 1× Official description updated · Oct 26, 2026 – Oct 26, 2026

References

2 on the record

Elsewhere on this site

Yeswiki
every CVE for this vendor
SSRF
same class
CWE-918
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-116828 YesWiki before 4.7.0 SQL Injection via despam.php INTERVAL operand 3d
  • Medium CVE-2026-116826 YesWiki before 4.7.0 Authenticated SSRF via Page Duplication API downloadFile 3d
  • Medium CVE-2026-116822 YesWiki before 4.7.0 Template Traversal via BazarListeAction template Parameter 3d
  • Medium CVE-2026-116823 YesWiki before 4.7.0 Reflected XSS via BazarField $_REQUEST Fallback 3d
  • Medium CVE-2026-116824 YesWiki before 4.7.0 Stored XSS via Referer Header in referrers_sites Handler 3d
  • Medium CVE-2026-116825 YesWiki from 4.6.2 before 4.7.0 HTTP Signature Replay via ActivityPub Inbox 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 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-116827 is "YesWiki before 4.7.0 SSRF via copyUrlToLocalFile in Bazar CSV Import", 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 6.8 describes technical severity. EPSS 0.35% 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.