CVE-2025-34076: Microweber CMS · Path Traversal
Affects Microweber CMSSource CVE Database V5
Not known to be exploited · public exploit available (Metasploit) · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microweber Ltd.CMS | Affected
| Fixed in– |
GitHubmicroweber/microweberpkg:github/microweber/microweberOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately upgrade Microweber CMS to a version that patches this vulnerability once available. 2. Until a patch is released, restrict access to the backup management API endpoints (/api/BackupV2/upload and /api/BackupV2/download) to trusted administrators only, using network-level controls such as IP whitelisting or VPN access. 3. Implement strict input validation and sanitization on the 'src' parameter to prevent absolute path usage and enforce directory restrictions. 4. Review and harden file system permissions for the web service user to limit the scope of accessible files and prevent unauthorized file operations. 5. Monitor logs for unusual API usage patterns indicative of exploitation attempts, such as unexpected file paths or frequent backup API calls. 6. Conduct regular audits of user accounts and privileges to reduce the risk of compromised credentials being used to exploit this vulnerability. 7. Employ web application firewalls (WAF) with custom rules to detect and block path traversal attempts targeting the backup API endpoints. 8. Educate administrators and developers on secure coding practices related to file handling and path validation to prevent similar issues in the future.
Description
An authenticated local file inclusion vulnerability exists in Microweber CMS versions <= 1.2.11 through misuse of the backup management API. Authenticated users can abuse the /api/BackupV2/upload and /api/BackupV2/download endpoints to read arbitrary files from the underlying filesystem. By specifying an absolute file path in the src parameter of the upload request, the server may relocate or delete the target file depending on the web service user’s privileges. The corresponding download endpoint can then be used to retrieve the file contents, effectively enabling local file disclosure. This behavior stems from insufficient validation of user-supplied paths and inadequate restrictions on file access and backup logic.
References
- raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/auxiliary/gather/microweber_lfi.rb (opens in a new tab)
- github.com/microweber/microweber (opens in a new tab)
- huntr.com/bounties/09218d3f-1f6a-48ae-981c-85e86ad5ed8b (opens in a new tab)
- github.com/microweber/microweber/commit/98d025467128ecc24195dcb56c533febc3c91af6 (opens in a new tab)
- github.com/microweber/microweber/commit/572bdc36b5b47923790016f6b961c8df53226855 (opens in a new tab)
- vulncheck.com/advisories/microweber-cms-lfi (opens in a new tab)