Skip to main content
CVE-2026-130359VulnerabilityPublished

AdminNeo before 5.9.1 contains a stored cross-site scripting vulnerability in SlugifyEditPlugin::getFieldInput() that

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130359· Low 2.0

Not known to be exploited · CVSS 2.0 Low : upgrade to 5.9.1 when convenient.

Data as of 17 Nov 2026, 05:03 UTC

CVSS 4.0 base score
2.0Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.02.0
CNA (VulnCheck)CVSS 3.12.6
Patch
Available – fixed in 5.9.1
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade AdminNeo to 5.9.1.

Affected software

ProductAffectedFixed in
adminneo-orgAdminNeoAffected
  • <5.9.1
Fixed in
  • 5.9.1
PackagistAdminNeopkg:composer/AdminNeoOther threatsAffected
  • <5.9.1
Fixed in
  • 5.9.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in AdminNeo version 5.9.1 and later. Users should upgrade to version 5.9.1 or newer to remediate this vulnerability. Since the vulnerability requires DDL privileges, restricting such privileges to trusted users also reduces risk. No other specific mitigations are indicated.

Description

AdminNeo versions prior to 5.9.1 have a stored cross-site scripting (XSS) vulnerability in the SlugifyEditPlugin::getFieldInput() function. This flaw occurs because column names are embedded unescaped in an inline initSlugField() call. Attackers with Data Definition Language (DDL) privileges can exploit this by creating a slug column with a single quote in its name, injecting JavaScript that executes under the page's Content Security Policy (CSP) nonce when users open the table's edit form.

References

Community reviews

Loading reviews…