PfsenseApplication
CVE-2025-69691
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNetgate pfSense CE 2.8.0 allows code execution in the XMLRPC API via pfsense.exec_php. NOTE: the Supplier disputes this because the API call is only available to admins and they are intentionally allowed to execute PHP code.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNetgate pfSense CE 2.8.0 contains an authenticated code execution vulnerability in the XMLRPC API through the pfsense.exec_php function. Attackers with administrative credentials can execute arbitrary PHP code on the underlying system via this API endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
PfsenseApplication
= 2.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify pfSense CE versionNavigate to System > Dashboard or check /etc/version file to determine the installed pfSense versionAffected if Version is exactly 2.8.0
-
Confirm XMLRPC API is accessibleCheck if the XMLRPC API endpoint is exposed. This is typically available at /xmlrpc.php or through the diagnostic XMLRPC sync settings at VPN > XMLRPC ConfigurationAffected if XMLRPC API endpoint responds to requests from the network or is enabled in system configuration
-
Identify administrative accountsReview user accounts with administrative privileges at System > User Manager. Look for users assigned to the Administrators groupAffected if Any administrative-level user accounts exist in the system
-
Check XMLRPC sync configurationExamine the XMLRPC synchronization settings at Status > Services or VPN > XMLRPC Configuration to determine if sync is enabledAffected if XMLRPC sync feature is enabled or configured on the firewall
-
Verify API exposureReview firewall rules and NAT settings to determine if the XMLRPC interface is reachable from untrusted networksAffected if The XMLRPC service is bound to an interface accessible from outside trusted network segments
A system is affected if it runs pfSense CE version 2.8.0 with XMLRPC API enabled and has administrative users that could be compromised to execute arbitrary PHP code through the pfsense.exec_php function.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict administrative access to trusted users only, implement network segmentation to limit API exposure, and consider disabling the XMLRPC API if not required or applying additional authentication layers.
Fix this in Pfsense
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69691 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-69691 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data