Security readout for executives and security teams
Plain-English summary
CVE-2014-4689 is a path traversal flaw in pfSense's WebGUI package editing code before version 2.1.4. A remote attacker could make the application read XML files by supplying a full file path. For a firewall appliance, even read-only file exposure can matter, but the provided sources do not include CVSS, authentication context, or exploitation evidence.
Executive priority
Treat as a moderate priority for legacy pfSense environments. This is old, not KEV-listed, and lacks severity scoring, but firewalls are sensitive control points. Confirm no pre-2.1.4 systems remain and ensure administrative WebGUI exposure is tightly controlled.
Technical view
The issue is an absolute path traversal vulnerability in pkg_edit.php affecting pfSense before 2.1.4. The CVE description says the xml parameter accepts a full pathname, allowing remote attackers to read arbitrary XML files. The source bundle does not identify CWE, CVSS metrics, authentication requirements, or exact file disclosure impact beyond XML files.
Likely exposure
Exposure is most likely on pfSense deployments older than 2.1.4 where the WebGUI route containing pkg_edit.php is reachable. The structured affected-product data is incomplete, so inventory should rely on pfSense version and WebGUI exposure rather than the empty CPE fields.
Exploitation context
CISA KEV status is false, and the provided sources do not cite active exploitation. The public CVE text describes the vulnerable parameter and impact, but does not provide exploit maturity, attacker prerequisites, or whether authentication is required.
Researcher notes
The available record is sparse: no CVSS, CWE, CPEs, authentication detail, or exploit-status evidence. Analysis should avoid assuming broader file disclosure than XML files. Focus validation on version, WebGUI reachability, and vendor advisory alignment.
Mitigation direction
- Upgrade affected pfSense systems to 2.1.4 or a current supported release.
- Review the pfSense advisory for vendor-confirmed remediation details.
- Restrict WebGUI access to trusted administrative networks only.
- Remove or replace unsupported pfSense versions from production use.
Validation and detection
- Inventory pfSense appliances and record exact running versions.
- Confirm no pfSense instance is older than 2.1.4.
- Verify WebGUI access is not exposed to untrusted networks.
- Review logs for unusual package editor requests, if retained.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
File access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2014-4689 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://pfsense.org/security/advisories/pfSense-SA-14_11.webgui.ascCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.