Webasyst Framework up to 4.4.0 Archive Symlink wa-config/db.php waArchiveTar::writeItem path traversal

Summaryinfo

A vulnerability, which was classified as problematic, was found in Webasyst Framework up to 4.4.0. This affects the function waArchiveTar::writeItem of the file wa-config/db.php of the component Archive Symlink Handler. Such manipulation leads to path traversal. This vulnerability is listed as CVE-2026-116213. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability was found in Webasyst Framework up to 4.4.0. It has been rated as problematic. Affected by this issue is the function waArchiveTar::writeItem of the file wa-config/db.php of the component Archive Symlink Handler. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. 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. Impacted is confidentiality. CVE summarizes:

Webasyst Framework through 4.4.0 contains an arbitrary file read vulnerability in waArchiveTar::writeItem() that creates symlinks from theme archives without validating link targets. Authenticated users with theme management rights can upload themes containing symlinks to wa-config/db.php or /etc/passwd and read them through the public theme path.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-116213 since 10/25/2026. The exploitation is known to be easy. The attack may be launched remotely. Additional levels of successful authentication are necessary for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1006.

By approaching the search of inurl:wa-config/db.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Webasyst

Name

• Framework

Version

• 4.0
• 4.1
• 4.2
• 4.3
• 4.4.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion