CVE-2019-16667

Public Exploit

Description

diag_command.php in pfSense 2.4.4-p3 allows CSRF via the txtCommand or txtRecallBuffer field, as demonstrated by executing OS commands. This occurs because csrf_callback() produces a "CSRF token expired" error and a Try Again button when a CSRF token is missing.

Category

8.8
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 49.21% Top 5%
Third-Party Advisory pastebin.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://pastebin.com/TEJdu9LN third party advisory exploit
http://packetstormsecurity.com/files/158614/pfSense-2.4.4-p3-Cross-Site-Request-Forgery.html

Frequently Asked Questions

What is the severity of CVE-2019-16667?
CVE-2019-16667 has been scored as a high severity vulnerability.
How to fix CVE-2019-16667?
To fix CVE-2019-16667, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-16667 being actively exploited in the wild?
It is possible that CVE-2019-16667 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~49% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.