Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2014-5084: A Command Execution vulnerability exists in Sphider Pro 3.2 due to insufficient sanitization of fwrite, which

59
This month
HIGH 8.8DOWNGRADE

CVE-2014-5084 is a high-severity flaw (CVSS 8.8) affecting sphider pro. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A Command Execution vulnerability exists in Sphider Pro 3.2 due to insufficient sanitization of fwrite, which could let a remote malicious user execute arbitrary code. CVE-2014-5084 pertains to instances of fwrite in Sphider Pro only, but do not exist in either Sphider or Sphider Plus.

Why this priority

  • High severity
  • EPSS top 5%: very likely to be exploited
  • Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance7.7% (top 5%)
CISA exploited listNo
WeaknessCWE-74
Published2020-02-10
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: sphiderpro

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

sphiderpro sphider pro DOWNGRADE
Affected: 3.2
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.2
1. Check installed version
apt-cache policy sphider-pro || rpm -q sphider-pro || sphider-pro --version
2. No fixed release: DOWNGRADE to a release before 3.2 (Debian / Ubuntu)
apt-cache madison sphider-pro sudo apt install sphider-pro=<VERSION_BEFORE_3.2> sudo apt-mark hold sphider-pro
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list sphider-pro sudo dnf downgrade sphider-pro-<VERSION_BEFORE_3.2> sudo dnf versionlock add sphider-pro
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2014-5084?

sphider pro: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2014-5084 being exploited?

CVE-2014-5084 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2014-5084 affect?

CVE-2014-5084 affects sphider pro. Severity is high (CVSS 8.8). A Command Execution vulnerability exists in Sphider Pro 3.2 due to insufficient sanitization of fwrite, which could let a remote malicious user execute arbitrary code. CVE-2014-5084 pertains to instances of fwrite in Sphider Pro only, but d

How urgent is CVE-2014-5084?

Priority 59/100. High severity; EPSS top 5%: very likely to be exploited; Public exploit reference

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.