CWE-22
Allowed-with-ReviewImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Abstraction: Base · Status: Stable
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
13069 vulnerabilities reference this CWE, most recent first.
GHSA-4WMM-6QXJ-FPJ4
Vulnerability from github – Published: 2026-03-19 12:43 – Updated: 2026-04-13 17:41Summary
The listFiles.json.php endpoint accepts a path POST parameter and passes it directly to glob() without restricting the path to an allowed base directory. An authenticated uploader can traverse the entire server filesystem by supplying arbitrary absolute paths, enumerating .mp4 filenames and their full absolute filesystem paths wherever they exist on the server — including locations outside the web root, such as private or premium media directories.
Details
The vulnerable code is at objects/listFiles.json.php:8-45:
if (!User::canUpload() || !empty($advancedCustom->doNotShowImportMP4Button)) {
return false;
}
$global['allowed'] = ['mp4'];
// ...
if (!empty($_POST['path'])) {
$path = $_POST['path'];
if (substr($path, -1) !== '/') {
$path .= "/";
}
if (file_exists($path)) {
$extn = implode(",*.", $global['allowed']);
$filesStr = "{*." . $extn . ",*." . strtolower($extn) . ",*." . strtoupper($extn) . "}";
$video_array = glob($path . $filesStr, GLOB_BRACE);
foreach ($video_array as $key => $value) {
$filePath = mb_convert_encoding($value, 'UTF-8');
// ...
$obj->path = $filePath; // Full absolute path returned to caller
The $_POST['path'] value is used directly in glob() with no call to realpath() for normalization and no prefix check against a permitted base directory (e.g., $global['systemRootPath'] . 'videos/'). The response includes obj->path containing the full absolute filesystem path of each matched file.
The extension filter ({*.mp4,*.mp4,*.MP4}) limits results to .mp4 files, which prevents reading credentials or source code but does not prevent enumeration of video files stored in access-controlled locations such as:
- Premium/paid content directories
- Private or unlisted media stores
- Backup directories containing .mp4 files
- Paths revealing sensitive server directory structure
canUpload is a standard low-privilege role granted to any registered uploader; it does not imply administrative trust.
PoC
# Step 1: Authenticate as any user with canUpload permission
# (standard uploader account)
# Step 2: Enumerate MP4 files in the web root (expected behavior)
curl -b "PHPSESSID=<session>" -X POST https://target.avideo.site/listFiles \
-d "path=/var/www/html/videos/"
# Returns: [{"id":0,"path":"/var/www/html/videos/video1.mp4","name":"video1.mp4"}, ...]
# Step 3: Traverse outside intended directory to private content store
curl -b "PHPSESSID=<session>" -X POST https://target.avideo.site/listFiles \
-d "path=/var/private/premium-content/"
# Returns: [{"id":0,"path":"/var/private/premium-content/paywalled-video.mp4","name":"paywalled-video.mp4"}, ...]
# Step 4: Enumerate root filesystem for any MP4 files
curl -b "PHPSESSID=<session>" -X POST https://target.avideo.site/listFiles \
-d "path=/"
# Returns all .mp4 files visible to the web server process anywhere on disk
Expected behavior: Only files within the designated upload directory should be listable. Actual behavior: Files from any path readable by the web server process are returned with full absolute paths.
Impact
- Unauthorized media enumeration: An uploader can discover private, premium, or access-controlled
.mp4files stored outside their permitted directory. - Filesystem structure disclosure: Full absolute paths reveal server directory layout, aiding further attacks.
- Content bypass: In AVideo deployments where premium video files are stored in filesystem directories not protected by application access control, this exposes the filenames and paths needed to directly access them if other path traversal or direct-file-access weaknesses are present.
- Blast radius: Requires
canUploadpermission (low privilege), but this is the standard permission for all video uploaders on a multi-user AVideo instance.
Recommended Fix
Restrict the supplied path to an allowed base directory using realpath():
if (!empty($_POST['path'])) {
$allowedBase = realpath($global['systemRootPath'] . 'videos') . '/';
$path = realpath($_POST['path']);
// Reject paths that don't start with the allowed base
if ($path === false || strpos($path . '/', $allowedBase) !== 0) {
http_response_code(403);
echo json_encode(['error' => 'Path not allowed']);
exit;
}
$path .= '/';
// ... continue with glob
}
realpath() resolves ../ sequences before the prefix check, preventing traversal bypasses.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 25.0"
},
"package": {
"ecosystem": "Packagist",
"name": "wwbn/avideo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "26.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-33238"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-19T12:43:42Z",
"nvd_published_at": "2026-03-21T00:16:26Z",
"severity": "MODERATE"
},
"details": "## Summary\n\nThe `listFiles.json.php` endpoint accepts a `path` POST parameter and passes it directly to `glob()` without restricting the path to an allowed base directory. An authenticated uploader can traverse the entire server filesystem by supplying arbitrary absolute paths, enumerating `.mp4` filenames and their full absolute filesystem paths wherever they exist on the server \u2014 including locations outside the web root, such as private or premium media directories.\n\n## Details\n\nThe vulnerable code is at `objects/listFiles.json.php:8-45`:\n\n```php\nif (!User::canUpload() || !empty($advancedCustom-\u003edoNotShowImportMP4Button)) {\n return false;\n}\n$global[\u0027allowed\u0027] = [\u0027mp4\u0027];\n// ...\nif (!empty($_POST[\u0027path\u0027])) {\n $path = $_POST[\u0027path\u0027];\n if (substr($path, -1) !== \u0027/\u0027) {\n $path .= \"/\";\n }\n if (file_exists($path)) {\n $extn = implode(\",*.\", $global[\u0027allowed\u0027]);\n $filesStr = \"{*.\" . $extn . \",*.\" . strtolower($extn) . \",*.\" . strtoupper($extn) . \"}\";\n $video_array = glob($path . $filesStr, GLOB_BRACE);\n foreach ($video_array as $key =\u003e $value) {\n $filePath = mb_convert_encoding($value, \u0027UTF-8\u0027);\n // ...\n $obj-\u003epath = $filePath; // Full absolute path returned to caller\n```\n\nThe `$_POST[\u0027path\u0027]` value is used directly in `glob()` with no call to `realpath()` for normalization and no prefix check against a permitted base directory (e.g., `$global[\u0027systemRootPath\u0027] . \u0027videos/\u0027`). The response includes `obj-\u003epath` containing the full absolute filesystem path of each matched file.\n\nThe extension filter (`{*.mp4,*.mp4,*.MP4}`) limits results to `.mp4` files, which prevents reading credentials or source code but does not prevent enumeration of video files stored in access-controlled locations such as:\n- Premium/paid content directories\n- Private or unlisted media stores\n- Backup directories containing `.mp4` files\n- Paths revealing sensitive server directory structure\n\n`canUpload` is a standard low-privilege role granted to any registered uploader; it does not imply administrative trust.\n\n## PoC\n\n```bash\n# Step 1: Authenticate as any user with canUpload permission\n# (standard uploader account)\n\n# Step 2: Enumerate MP4 files in the web root (expected behavior)\ncurl -b \"PHPSESSID=\u003csession\u003e\" -X POST https://target.avideo.site/listFiles \\\n -d \"path=/var/www/html/videos/\"\n# Returns: [{\"id\":0,\"path\":\"/var/www/html/videos/video1.mp4\",\"name\":\"video1.mp4\"}, ...]\n\n# Step 3: Traverse outside intended directory to private content store\ncurl -b \"PHPSESSID=\u003csession\u003e\" -X POST https://target.avideo.site/listFiles \\\n -d \"path=/var/private/premium-content/\"\n# Returns: [{\"id\":0,\"path\":\"/var/private/premium-content/paywalled-video.mp4\",\"name\":\"paywalled-video.mp4\"}, ...]\n\n# Step 4: Enumerate root filesystem for any MP4 files\ncurl -b \"PHPSESSID=\u003csession\u003e\" -X POST https://target.avideo.site/listFiles \\\n -d \"path=/\"\n# Returns all .mp4 files visible to the web server process anywhere on disk\n```\n\n**Expected behavior:** Only files within the designated upload directory should be listable.\n**Actual behavior:** Files from any path readable by the web server process are returned with full absolute paths.\n\n## Impact\n\n- **Unauthorized media enumeration:** An uploader can discover private, premium, or access-controlled `.mp4` files stored outside their permitted directory.\n- **Filesystem structure disclosure:** Full absolute paths reveal server directory layout, aiding further attacks.\n- **Content bypass:** In AVideo deployments where premium video files are stored in filesystem directories not protected by application access control, this exposes the filenames and paths needed to directly access them if other path traversal or direct-file-access weaknesses are present.\n- **Blast radius:** Requires `canUpload` permission (low privilege), but this is the standard permission for all video uploaders on a multi-user AVideo instance.\n\n## Recommended Fix\n\nRestrict the supplied path to an allowed base directory using `realpath()`:\n\n```php\nif (!empty($_POST[\u0027path\u0027])) {\n $allowedBase = realpath($global[\u0027systemRootPath\u0027] . \u0027videos\u0027) . \u0027/\u0027;\n $path = realpath($_POST[\u0027path\u0027]);\n\n // Reject paths that don\u0027t start with the allowed base\n if ($path === false || strpos($path . \u0027/\u0027, $allowedBase) !== 0) {\n http_response_code(403);\n echo json_encode([\u0027error\u0027 =\u003e \u0027Path not allowed\u0027]);\n exit;\n }\n $path .= \u0027/\u0027;\n // ... continue with glob\n}\n```\n\n`realpath()` resolves `../` sequences before the prefix check, preventing traversal bypasses.",
"id": "GHSA-4wmm-6qxj-fpj4",
"modified": "2026-04-13T17:41:29Z",
"published": "2026-03-19T12:43:42Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-4wmm-6qxj-fpj4"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33238"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/issues/10403"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/commit/870cf24a7632d4f1a5d5549b59103c18f39e3a21"
},
{
"type": "PACKAGE",
"url": "https://github.com/WWBN/AVideo"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "AVideo has a Path Traversal in listFiles.json.php Enables Server Filesystem Enumeration"
}
GHSA-4WPM-WJ3C-MR8R
Vulnerability from github – Published: 2024-12-06 15:31 – Updated: 2024-12-06 15:31The Swift Performance Lite plugin for WordPress is vulnerable to Local PHP File Inclusion in all versions up to, and including, 2.3.7.1 via the 'ajaxify' function. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
{
"affected": [],
"aliases": [
"CVE-2024-10516"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-12-06T14:15:19Z",
"severity": "HIGH"
},
"details": "The Swift Performance Lite plugin for WordPress is vulnerable to Local PHP File Inclusion in all versions up to, and including, 2.3.7.1 via the \u0027ajaxify\u0027 function. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other \u201csafe\u201d file types can be uploaded and included.",
"id": "GHSA-4wpm-wj3c-mr8r",
"modified": "2024-12-06T15:31:19Z",
"published": "2024-12-06T15:31:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-10516"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/swift-performance-lite/trunk/includes/classes/class.ajax.php#L795"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/swift-performance-lite/trunk/includes/classes/class.ajax.php#L824"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3201933"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/4921f41a-a9b1-4ae2-a903-c14ed22dcc15?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-4WQ8-9VVH-C555
Vulnerability from github – Published: 2025-08-13 21:30 – Updated: 2025-11-05 00:31UnForm Server Manager versions prior to 10.1.12 expose an unauthenticated file read vulnerability via its log file analysis interface. The flaw resides in the arc endpoint, which accepts a fl parameter to specify the log file to be opened. Due to insufficient input validation and lack of path sanitization, attackers can supply relative paths to access arbitrary files on the host system — including sensitive OS-level files — without authentication.
{
"affected": [],
"aliases": [
"CVE-2025-34154"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-13T21:15:33Z",
"severity": "CRITICAL"
},
"details": "UnForm Server Manager versions prior to 10.1.12 expose an unauthenticated file read vulnerability via its log file analysis interface. The flaw resides in the arc endpoint, which accepts a fl parameter to specify the log file to be opened. Due to insufficient input validation and lack of path sanitization, attackers can supply relative paths to access arbitrary files on the host system \u2014 including sensitive OS-level files \u2014 without authentication.",
"id": "GHSA-4wq8-9vvh-c555",
"modified": "2025-11-05T00:31:24Z",
"published": "2025-08-13T21:30:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-34154"
},
{
"type": "WEB",
"url": "https://gist.github.com/Janrdrz/3cf67a9ad488e07ceaacd7c1a7e59ae7"
},
{
"type": "WEB",
"url": "https://synergetic-data.com"
},
{
"type": "WEB",
"url": "https://unform.com/download/uf101_readme.txt"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/unform-server-manager-unauthenticated-arbitrary-file-read"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-4WQ8-FWF6-XQWM
Vulnerability from github – Published: 2022-05-17 02:39 – Updated: 2022-05-17 02:39Directory traversal vulnerability in ManageEngine Firewall Analyzer before 8.0.
{
"affected": [],
"aliases": [
"CVE-2015-7780"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-06-27T20:29:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in ManageEngine Firewall Analyzer before 8.0.",
"id": "GHSA-4wq8-fwf6-xqwm",
"modified": "2022-05-17T02:39:20Z",
"published": "2022-05-17T02:39:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-7780"
},
{
"type": "WEB",
"url": "http://jvn.jp/en/jp/JVN21968837/index.html"
},
{
"type": "WEB",
"url": "http://jvndb.jvn.jp/ja/contents/2015/JVNDB-2015-000185.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-4WQW-89QW-8R56
Vulnerability from github – Published: 2026-06-12 06:33 – Updated: 2026-06-12 06:33A malicious actor with access to the network could exploit a Path Traversal vulnerability found in certain devices running UniFi OS to obtain data from such UniFi OS devices or instances.
{
"affected": [],
"aliases": [
"CVE-2026-47368"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-12T04:17:06Z",
"severity": "HIGH"
},
"details": "A malicious actor with access to the network could exploit a Path Traversal vulnerability found in certain devices running UniFi OS to obtain data from such UniFi OS devices or instances.",
"id": "GHSA-4wqw-89qw-8r56",
"modified": "2026-06-12T06:33:20Z",
"published": "2026-06-12T06:33:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-47368"
},
{
"type": "WEB",
"url": "https://community.ui.com/releases/Security-Advisory-Bulletin-065-065/aa46a22b-fc43-4eae-9382-6fc8feda967a"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-4WRM-QMQ2-5FJX
Vulnerability from github – Published: 2023-12-08 21:30 – Updated: 2023-12-13 13:36Directory Traversal vulnerability in EverShop NPM versions before v.1.0.0-rc.8 allows a remote attacker to obtain sensitive information via a crafted request to the readDirSync function in fileBrowser/browser.js.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "@evershop/evershop"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.0-rc.8"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2023-46493"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2023-12-13T13:36:13Z",
"nvd_published_at": "2023-12-08T20:15:07Z",
"severity": "MODERATE"
},
"details": "Directory Traversal vulnerability in EverShop NPM versions before v.1.0.0-rc.8 allows a remote attacker to obtain sensitive information via a crafted request to the readDirSync function in fileBrowser/browser.js.",
"id": "GHSA-4wrm-qmq2-5fjx",
"modified": "2023-12-13T13:36:13Z",
"published": "2023-12-08T21:30:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-46493"
},
{
"type": "WEB",
"url": "https://github.com/evershopcommerce/evershop/pull/338"
},
{
"type": "WEB",
"url": "https://devhub.checkmarx.com/cve-details/CVE-2023-46493"
},
{
"type": "WEB",
"url": "https://devhub.checkmarx.com/cve-details/Cxa4d94170-be41"
},
{
"type": "PACKAGE",
"url": "https://github.com/evershopcommerce/evershop"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Directory Traversal in evershop"
}
GHSA-4WRR-WX49-F3MW
Vulnerability from github – Published: 2023-02-16 21:30 – Updated: 2023-02-25 00:30A relative path traversal vulnerability [CWE-23] in FortiWeb 7.0.0 through 7.0.1, 6.3.6 through 6.3.18, 6.4 all versions may allow an authenticated attacker to obtain unauthorized access to files and data via specifically crafted HTTP GET requests.
{
"affected": [],
"aliases": [
"CVE-2022-30300"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-02-16T19:15:00Z",
"severity": "MODERATE"
},
"details": "A relative path traversal vulnerability [CWE-23] in FortiWeb 7.0.0 through 7.0.1, 6.3.6 through 6.3.18, 6.4 all versions may allow an authenticated attacker to obtain unauthorized access to files and data via specifically crafted HTTP GET requests.",
"id": "GHSA-4wrr-wx49-f3mw",
"modified": "2023-02-25T00:30:46Z",
"published": "2023-02-16T21:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-30300"
},
{
"type": "WEB",
"url": "https://fortiguard.com/psirt/FG-IR-22-136"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-4WWR-56PJ-4V9H
Vulnerability from github – Published: 2023-12-16 03:30 – Updated: 2023-12-20 18:30Path traversal vulnerability in AVEVA Edge (formerly InduSoft Web Studio) versions R2020 and prior allows an unauthenticated user to steal the Windows access token of the user account configured for accessing external DB resources.
{
"affected": [],
"aliases": [
"CVE-2021-42797"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-12-16T01:15:07Z",
"severity": "HIGH"
},
"details": "Path traversal vulnerability in AVEVA Edge (formerly InduSoft Web Studio) versions R2020 and prior allows an unauthenticated user to steal the Windows access token of the user account configured for accessing external DB resources.",
"id": "GHSA-4wwr-56pj-4v9h",
"modified": "2023-12-20T18:30:32Z",
"published": "2023-12-16T03:30:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-42797"
},
{
"type": "WEB",
"url": "https://www.aveva.com/en/products/edge"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/news-events/ics-advisories/icsa-22-326-01"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-4WXW-W756-WVC6
Vulnerability from github – Published: 2025-03-31 18:31 – Updated: 2025-03-31 18:31Xorcom CompletePBX is vulnerable to a path traversal via the Diagnostics reporting module, which will allow reading of arbitrary files and additionally delete any retrieved file in place of the expected report.
This issue affects CompletePBX: all versions up to and prior to 5.2.35
{
"affected": [],
"aliases": [
"CVE-2025-30005"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-03-31T17:15:41Z",
"severity": "MODERATE"
},
"details": "Xorcom CompletePBX is vulnerable to a path traversal via the Diagnostics reporting module, which will allow reading of arbitrary files and additionally delete any retrieved file in place of the expected report.\n\n\n\n\nThis issue affects CompletePBX: all versions up to and prior to 5.2.35",
"id": "GHSA-4wxw-w756-wvc6",
"modified": "2025-03-31T18:31:08Z",
"published": "2025-03-31T18:31:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-30005"
},
{
"type": "WEB",
"url": "https://vulncheck.com/advisories/completepbx-path-traversal-file-deletion"
},
{
"type": "WEB",
"url": "https://www.xorcom.com/new-completepbx-release-5-2-36-1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-4X28-J85R-668Q
Vulnerability from github – Published: 2022-05-17 01:48 – Updated: 2024-01-12 18:02Directory traversal vulnerability in frontend/core/engine/javascript.php in Fork CMS 3.2.4 and possibly other versions before 3.2.5 allows remote attackers to read arbitrary files via a .. (dot dot) in the module parameter to frontend/js.php.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 3.2.4"
},
"package": {
"ecosystem": "Packagist",
"name": "forkcms/forkcms"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.2.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2012-1207"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2024-01-12T18:02:51Z",
"nvd_published_at": "2012-02-24T13:55:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in `frontend/core/engine/javascript.php` in Fork CMS 3.2.4 and possibly other versions before 3.2.5 allows remote attackers to read arbitrary files via a `..` (dot dot) in the module parameter to `frontend/js.php`.",
"id": "GHSA-4x28-j85r-668q",
"modified": "2024-01-12T18:02:51Z",
"published": "2022-05-17T01:48:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-1207"
},
{
"type": "WEB",
"url": "https://github.com/forkcms/forkcms/commit/a9986b86c53de0582248b39605660fbba0c21a29"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/73169"
},
{
"type": "PACKAGE",
"url": "https://github.com/forkcms/forkcms"
},
{
"type": "WEB",
"url": "https://web.archive.org/web/20120401204340/http://www.securityfocus.com/bid/51972"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.org/files/109709/Fork-CMS-3.2.4-Cross-Site-Scripting-Local-File-Inclusion.html"
},
{
"type": "WEB",
"url": "http://www.fork-cms.com/blog/detail/fork-cms-3-2-5-released"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "ForkCMS Directory Traversal vulnerability"
}
Mitigation MIT-5.1
Strategy: Input Validation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.
- Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.
Mitigation MIT-15
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Mitigation MIT-20.1
Strategy: Input Validation
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
- Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59). This includes:
- realpath() in C
- getCanonicalPath() in Java
- GetFullPath() in ASP.NET
- realpath() or abs_path() in Perl
- realpath() in PHP
Mitigation MIT-4
Strategy: Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
Mitigation MIT-29
Strategy: Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
Mitigation MIT-17
Strategy: Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
Mitigation MIT-21.1
Strategy: Enforcement by Conversion
- When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
- For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap [REF-185] provide this capability.
Mitigation MIT-22
Strategy: Sandbox or Jail
- Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
- OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
- This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
- Be careful to avoid CWE-243 and other weaknesses related to jails.
Mitigation MIT-34
Strategy: Attack Surface Reduction
- Store library, include, and utility files outside of the web document root, if possible. Otherwise, store them in a separate directory and use the web server's access control capabilities to prevent attackers from directly requesting them. One common practice is to define a fixed constant in each calling program, then check for the existence of the constant in the library/include file; if the constant does not exist, then the file was directly requested, and it can exit immediately.
- This significantly reduces the chance of an attacker being able to bypass any protection mechanisms that are in the base program but not in the include files. It will also reduce the attack surface.
Mitigation MIT-39
- Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
- If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
- Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
- In the context of path traversal, error messages which disclose path information can help attackers craft the appropriate attack strings to move through the file system hierarchy.
Mitigation MIT-16
Strategy: Environment Hardening
When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.
CAPEC-126: Path Traversal
An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attacker providing a complete path to a targeted file or using control characters (e.g. path separators (/ or \) and/or dots (.)) to reach desired directories or files.
CAPEC-64: Using Slashes and URL Encoding Combined to Bypass Validation Logic
This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.
CAPEC-76: Manipulating Web Input to File System Calls
An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
CAPEC-78: Using Escaped Slashes in Alternate Encoding
This attack targets the use of the backslash in alternate encoding. An adversary can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the adversary tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
CAPEC-79: Using Slashes in Alternate Encoding
This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.