CVE-2026-30868: Cross-Site Request Forgery (CSRF) in opnsense/core

Published Mar 11, 2026
·
Updated

OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.4, multiple OPNsense MVC API endpoints perform state‑changing operations but are accessible via HTTP GET requests without CSRF protection. The framework CSRF validation in ApiControllerBase only applies to POST/PUT/DELETE methods, allowing authenticated GET requests to bypass CSRF verification. As a result, a malicious website can trigger privileged backend actions when visited by an authenticated user, causing unintended service reloads and configuration changes through configd. This results in an authenticated Cross‑Site Request Forgery vulnerability allowing unauthorized system state changes. This vulnerability is fixed in 26.1.4.

Affected Software

2 affected components
OPNsense core<26.1.4
OPNsense OPNsense<26.1.4

Event History

Mar 11, 2026
CVE Published
via MITRE·04:38 PM
Data Sourced
via MITRE·04:38 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-30868?

CVE-2026-30868 has a severity rating that indicates a significant risk due to the potential for unauthorized changes via CSRF attacks.

2

How do I fix CVE-2026-30868?

Fix CVE-2026-30868 by updating OPNsense core to version 26.1.4 or newer to ensure CSRF protection is implemented.

3

Which versions of OPNsense core are affected by CVE-2026-30868?

CVE-2026-30868 affects all versions of OPNsense core prior to 26.1.4.

4

What kind of attack does CVE-2026-30868 facilitate?

CVE-2026-30868 facilitates Cross-Site Request Forgery (CSRF) attacks that can allow unauthorized actions to be performed by an attacker.

5

Are there any mitigation strategies for CVE-2026-30868?

While upgrading to a secure version is the best solution, employing web application firewalls or monitoring could help mitigate risks until the patch is applied.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203