MEDIUM 5.4

CVE-2026-14636: Path Traversal in Ecommerce-CodeIgniter-Bootstrap Vendor Image Manager

A path traversal vulnerability exists in the Ecommerce-CodeIgniter-Bootstrap project's vendor image upload feature. When authenticated users upload images through the Vendor Image Manager, an attacker can manipulate the folder parameter to access or write files outside the intended upload directory. The flaw is remotely exploitable by any logged-in user and requires no special interaction. This is a medium-severity issue affecting file integrity and confidentiality for systems using the vulnerable codebase.

Source data · NVD / CISA · public domain

CVSS
3.1 · 5.4 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Weaknesses (CWE)
CWE-22
Affected products
0 configuration(s)
Published / Modified
2026-07-04 / 2026-07-06

NVD description (verbatim)

A weakness has been identified in kirilkirkov Ecommerce-CodeIgniter-Bootstrap up to 23105f25dadf57b4314fc015a63a7c6e910c89df. Impacted is the function do_upload_others_images of the file application/modules/vendor/controllers/AddProduct.php of the component Vendor Image Manager. Executing a manipulation of the argument folder can lead to path traversal. It is possible to launch the attack remotely. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. This patch is called de1c9e73ccf3bd032d9a0525c4752290d959dd8b. It is best practice to apply a patch to resolve this issue.

8 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-14636 is a path traversal vulnerability (CWE-22) in the do_upload_others_images function within application/modules/vendor/controllers/AddProduct.php. The vulnerability arises from insufficient validation of the folder parameter, permitting directory traversal sequences (e.g., ../) to be passed through to file operations. An authenticated attacker can exploit this to read, modify, or delete files outside the designated upload directory, limited only by the web server's filesystem permissions. The CVSS 3.1 score of 5.4 (Medium) reflects low attack complexity, network accessibility, and authentication requirement, with integrity and availability impact but no confidentiality breach.

Business impact

Compromise of image management functionality could allow malicious users to corrupt application files, inject web shells into accessible directories, or overwrite critical configuration files. For e-commerce platforms, this may lead to defacement, data tampering, or lateral movement within the application infrastructure. The risk is elevated in multi-tenant or high-permission environments where vendor accounts are numerous or insufficiently isolated.

Affected systems

The vulnerability affects kirilkirkov Ecommerce-CodeIgniter-Bootstrap up to commit 23105f25dadf57b4314fc015a63a7c6e910c89df. Because this project uses rolling releases without traditional version numbers, the exact scope of affected installations cannot be specified from version strings alone. Any deployment of the project prior to patch commit de1c9e73ccf3bd032d9a0525c4752290d959dd8b is potentially at risk. Organizations must verify their current commit hash against both affected and patched commit hashes.

Exploitability

Exploitation requires valid vendor or admin credentials—a significant barrier that prevents anonymous abuse. However, the low attack complexity and straightforward nature of path traversal make this trivial to weaponize once authentication is achieved. Risk is highest in environments where vendor accounts are loosely managed, shared, or where non-technical vendors have upload privileges. No known public exploit code exists at this time, and the vulnerability is not tracked in the CISA Known Exploited Vulnerabilities catalog.

Remediation

Apply patch commit de1c9e73ccf3bd032d9a0525c4752290d959dd8b immediately. The patch likely strengthens input validation on the folder parameter and restricts path operations to a designated safe directory tree. After patching, review vendor account privileges and implement least-privilege access controls. Conduct a forensic review of upload directories to identify any suspicious files or unauthorized modifications dating back to deployment.

Patch guidance

Since this project follows rolling releases, update to a commit at or after de1c9e73ccf3bd032d9a0525c4752290d959dd8b. Verify the patch has been applied by inspecting the AddProduct.php file or by comparing your repository's current HEAD commit against the patch hash. If using a version-locked deployment, retrieve the latest upstream code and test thoroughly in a staging environment before production rollout. No official release notes or version numbers are available; rely on commit hashes and vendor advisories for confirmation.

Detection guidance

Monitor web server access logs for suspicious patterns in upload requests, particularly those containing ../ or similar traversal sequences in POST parameters or multipart form data. Review filesystem access logs (auditd on Linux) for unauthorized reads or writes outside the designated upload directory during vendor upload activity. Implement file integrity monitoring on critical application configuration files. Search application logs for error messages indicating permission denied or path normalization failures in the vendor upload module.

Why prioritize this

This vulnerability should be patched promptly despite its Medium CVSS score because (1) it requires only authenticated user access, which many e-commerce platforms grant freely; (2) path traversal is a well-understood and easily exploitable attack class; (3) successful exploitation can result in webshell placement or configuration tampering; and (4) the rolling release model makes it difficult to inventory affected instances, increasing uncertainty around exposure scope. Organizations with large vendor populations or integration with third-party systems should treat this as high priority.

Risk score, explained

The CVSS 3.1 score of 5.4 reflects a network-accessible, low-complexity vulnerability requiring authentication. Integrity and availability impacts are rated Low because the attack depends on destination file permissions and does not guarantee confidentiality breach. The score would be higher if unauthenticated access were possible or if confidentiality were assured; it remains Medium rather than High due to the authentication gate and environmental constraints.

Frequently asked questions

How do I know if my installation is vulnerable?

Identify your current commit hash and compare it against the affected commit (23105f25dadf57b4314fc015a63a7c6e910c89df). If your commit predates or matches the affected commit, and you have not manually patched to de1c9e73ccf3bd032d9a0525c4752290d959dd8b or later, your installation is vulnerable. Check your repository's git log or query the main branch's head commit.

Can this vulnerability be exploited without a vendor account?

No. The vulnerability exists in the vendor image upload functionality and requires valid credentials with vendor or administrative role. However, if credentials are shared, leaked, or assigned to untrusted users, the barrier to exploitation is minimal.

What files can an attacker access or modify?

An attacker can read or modify any file within the web server's writable filesystem scope and the application's permission context. This typically includes application code, configuration files, and other project files outside the upload directory. The exact scope depends on server configuration and filesystem permissions.

Does this vulnerability affect CodeIgniter itself?

No. This vulnerability is specific to the Ecommerce-CodeIgniter-Bootstrap project's implementation and not a CodeIgniter framework vulnerability. CodeIgniter users employing this particular project should update; CodeIgniter itself does not require patching for this issue.

This analysis is based on information available as of the publication date and the structural details provided in the CVE record. Because Ecommerce-CodeIgniter-Bootstrap uses rolling releases without traditional versioning, installations must be individually verified against commit hashes. Patch availability and effectiveness should be confirmed against the official project repository. This explainer does not constitute professional security advice; consult your organization's security team and vendor documentation before implementing any mitigations. SEC.co makes no warranty regarding the completeness or accuracy of affected product lists or patch details—always verify against official vendor advisories and your specific deployment configuration. Source: NVD (public-domain), retrieved 2026-08-13. Analysis generated by SEC.co (claude-haiku-4-5).