How severe is CVE-2018-7667?

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

Which packages are affected by CVE-2018-7667?

CVE-2018-7667 affects the following packages: vrana/adminer (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-7667?

Update vrana/adminer to 4.7.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-7667 is resolved across your whole dependency graph.

How do I detect CVE-2018-7667 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vrana/adminer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-7667 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

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

Yes. There are 1 known exploit references for CVE-2018-7667, including 1 in-the-wild exploitation 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-7667?

CVE-2018-7667 has an EPSS (Exploit Prediction Scoring System) score of 5.0%, placing it in the 92th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-7667?

CVE-2018-7667 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

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

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2018-7667 — adminer

CRITICALFix: vrana/adminer@35bfaa7

CVE-2018-7667 is a critical-severity (CVSS 9.8) Server-Side Request Forgery (SSRF) vulnerability in vrana/adminer. 1 public exploit reference exists, so weaponization risk is real. A fix is available for vrana/adminer — see the affected versions and patch details below.

vrana/adminer vulnerable to SSRF by connecting to privileged ports

Also known asGHSA-43f8-p5w3-5m25

Published

Mar 5, 2018

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

5.0%probability of exploitation in next 30 days

Lower Risk+0.53%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2018-7667 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,492 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐘vrana/adminer

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

All users are affected.

Patches

Unsuccessfully patched by 0fae40fb, included in version 4.4.0.
Patched by 35bfaa75, included in version 4.7.8.

Workarounds

Protect access to Adminer also by other means, e.g. by HTTP password, IP address limiting or by OTP plugin.

References

For more information

If you have any questions or comments about this advisory:

Comment at 35bfaa75.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`vrana/adminer`	all versions	4.7.8`composer require vrana/adminer:^4.7.8`

Affected Products

1 product · 1 configurations

Application

admineradminer

≤ 4.3.1

range

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.

Adminer through 4.3.1 has SSRF via the server parameter.

hyp3rlinx.altervista.orgNVDMar 2018

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vrana/adminer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vrana/adminer to 4.7.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-7667 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

### Impact All users are affected. ### Patches * Unsuccessfully patched by 0fae40fb, included in version [4.4.0](https://github.com/vrana/adminer/releases/tag/v4.4.0). * Patched by 35bfaa75, included in version [4.7.8](https://github.com/vrana/adminer/releases/tag/v4.7.8). ### Workarounds Protect access to Adminer also by other means, e.g. by HTTP password, IP address limiting or by OTP [plugin](https://www.adminer.org/plugins/). ### References * http://hyp3rlinx.altervista.org/advisories/ADMINER-UNAUTHENTICATED-SERVER-SIDE-REQUEST-FORGERY.txt * https://sourceforge.net/p/adminer/bugs-and-fe