Skip to content
Fencer Intel
medium 5.5

CVE-2018-13980 json

The websites that were built from Zeta Producer Desktop CMS before 14.2.1 are vulnerable to unauthenticated file disclosure if the plugin "…

published 8y ago modified 4mo ago also EUVD-2018-5914

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.9%
EPSS 6.9% chance of exploitation in 30 days, percentile 94%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

The websites that were built from Zeta Producer Desktop CMS before 14.2.1 are vulnerable to unauthenticated file disclosure if the plugin "filebrowser" is installed, because of assets/php/filebrowser/filebrowser.main.php?file=../ directory traversal.

Patch / fix

  • zeta-producer zeta_producer 14.2.1

Is CVE-2018-13980 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (EDB-45016)
  2. Published

Exploit prediction

6.90% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-45016 Zeta Producer Desktop CMS 14.2.0 - Remote Code Execution / Local File Disclosure webapps, 2018-07-13
  • Nuclei template Zeta Producer Desktop CMS <14.2.1 - Local File Inclusion nuclei detection template
  • packetstormsecurity.com http://packetstormsecurity.com/files/148537/Zeta-Producer-Desktop-CMS-14.2.0-Code-Execution-File-Disclosure.html referenced PoC, tagged "exploit" by a source, unverified
  • sec-consult.com https://www.sec-consult.com/en/blog/advisories/remote-code-execution-local-file-disclosure-zeta-producer-desktop-cms/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.