Skip to content
Fencer Intel
critical 9.8

CVE-2018-11535 json

An issue was discovered in SITEMAKIN SLAC (Site Login and Access Control) v1.0.

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

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
1
Exploit-DB

Summary

An issue was discovered in SITEMAKIN SLAC (Site Login and Access Control) v1.0. The parameter "my_item_search" in users.php is exploitable using SQL injection.

Is CVE-2018-11535 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-44793)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-44793 Sitemakin SLAC 1.0 - 'my_item_search' SQL Injection webapps, 2018-05-29
  • gist.github.com https://gist.github.com/NinjaXshell/f894bd79f9707a92a7b6934711a8fdc9 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

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.