Skip to content
Fencer Intel
medium 6.5

CVE-2015-7309 json

The theme editor in Bolt before 2.2.5 does not check the file extension when renaming files, which allows remote authenticated users to exe…

published 11y ago modified 4mo ago also EUVD-2015-7238

cvss
6.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
38.6%
EPSS 38.6% chance of exploitation in 30 days, percentile 98%
public exploits
2
Metasploit and Exploit-DB

Summary

The theme editor in Bolt before 2.2.5 does not check the file extension when renaming files, which allows remote authenticated users to execute arbitrary code by renaming a crafted file and then directly accessing it.

Patch / fix

Is CVE-2015-7309 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/multi/http/bolt_file_upload)
  2. Published

Exploit prediction

38.61% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/multi/http/bolt_file_upload CMS Bolt File Upload Vulnerability metasploit exploit, excellent rank, 2015-08-17
  • EDB-38196 CMS Bolt - Arbitrary File Upload (Metasploit) remote, 2015-09-15
  • packetstormsecurity.com http://packetstormsecurity.com/files/133539/CMS-Bolt-2.2.4-File-Upload.html referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2015/Aug/66 referenced PoC, tagged "exploit" by a source, unverified
  • blog.curesec.com http://blog.curesec.com/article/blog/Bolt-224-Code-Execution-44.html referenced PoC, tagged "exploit" by a source, unverified
  • rapid7.com http://www.rapid7.com/db/modules/exploit/multi/http/bolt_file_upload referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.