CVE-2026-56127: pfSense Plus < 26.07 / CE < 2.9.0 Stored XSS via firewall_rules_edit.php

Published Sep 3, 2026
·
Updated

pfSense Plus before 26.07 and CE before 2.9.0 allow authenticated users with the Firewall: Rules: Edit privilege to inject arbitrary JavaScript via the descr parameter in /firewallrulesedit.php. The firewall rule description is stored in the pfSense XML configuration with only backslash-escaping applied and no HTML sanitization, then rendered without encoding in the firewall log table in /statuslogsfilter.php. The payload executes in the browser of any user with the Status: Logs: Firewall privilege who views the affected log entries.

Affected Software

3 affected components
pfSense Plus<26.07
pfSense Plus>0<26.07
pfSense CE<2.9.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pfSense Plus to a version that resolves this vulnerability.

    Fixed in 26.07
  2. Upgrade

    Upgrade pfSense CE to a version that resolves this vulnerability.

    Fixed in 2.9.0
  3. Compensating control

    Until upgrading, restrict access to pfSense Status: Logs: Firewall and ensure only trusted users with the Status: Logs: Firewall privilege can view firewall log table entries (e.g., limit the privilege via authentication/role controls).

  4. Compensating control

    Until upgrading, restrict access to the Firewall: Rules: Edit privilege so only trusted administrators can edit firewall rules (limit who can access firewall_rules_edit.php/descr injection).

Event History

Sep 3, 2026
CVE Published
via MITRE·02:21 PM
Data Sourced
via MITRE·02:21 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which users can inject the malicious content, and which users are at risk of executing it?

An authenticated user needs the Firewall: Rules: Edit privilege to inject JavaScript through a firewall rule description. The script executes when a user with the Status: Logs: Firewall privilege views affected entries in the firewall log table.

2

What application behavior makes this issue persistent?

The supplied rule description is stored in the pfSense XML configuration with only backslash escaping and without HTML sanitization. It is later rendered in /status_logs_filter.php without encoding, allowing the stored payload to execute in a viewer's browser.

3

Which releases are affected?

pfSense Plus releases before 26.07 and pfSense CE releases before 2.9.0 are affected.

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