How severe is CVE-2018-1000533?

CVE-2018-1000533 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-1000533?

Affected package information for CVE-2018-1000533 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2018-1000533?

No fixed version has been published for CVE-2018-1000533 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2018-1000533 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2018-1000533, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-1000533?

CVE-2018-1000533 has an EPSS (Exploit Prediction Scoring System) score of 92.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2018-1000533?

CVE-2018-1000533 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2018-1000533?

A Nuclei detection template exists for CVE-2018-1000533, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2018-1000533 published, and has it been updated?

CVE-2018-1000533 was published on June 26, 2018 and was last updated on March 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2018-1000533

CRITICAL

Published

Jun 26, 2018

Updated

Mar 14, 2026

Affected

0 pkgs

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

92.4%probability of exploitation in next 30 days

Very High Risk100th percentile-0.72%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

klaussilveira GitList version <= 0.6 contains a Passing incorrectly sanitized input to system function vulnerability in searchTree function that can result in Execute any code as PHP user. This attack appear to be exploitable via Send POST request using search form. This vulnerability appears to have been fixed in 0.7 after commit 87b8c26b023c3fc37f0796b14bb13710f397b322.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

klaussilveira GitList version <= 0.6 contains a Passing incorrectly sani…

security.szurek.plNVDAug 2018

klaussilveira GitList version <= 0.6 contains a Passing incorrectly sani…

github.comMetasploitOct 2020

Frequently Asked Questions

klaussilveira GitList version <= 0.6 contains a Passing incorrectly sanitized input to system function vulnerability in `searchTree` function that can result in Execute any code as PHP user. This attack appear to be exploitable via Send POST request using search form. This vulnerability appears to have been fixed in 0.7 after commit 87b8c26b023c3fc37f0796b14bb13710f397b322.

O3 Security · Impact-Aware SCA

Is CVE-2018-1000533 in your stack?

O3 detects CVE-2018-1000533 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works