CVE-2011-4451
What it is
libs/Wakka.class.php in WikkaWiki 1.3.1 and 1.3.2, when the spam_logging option is enabled, allows remote attackers to write arbitrary PHP code to the spamlog_path file via the User-Agent HTTP header in an addcomment request. NOTE: the vendor disputes this issue because the rendering of the spamlog_path file never uses the PHP interpreter
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 14.2% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 14.2% in the next 30 days (EPSS).
- Severity: 4.3 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 14.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Wikkawiki 1.3.1
- Wikkawiki 1.3.2
Attack profile CVSS 2.0 · 4.3
- Attack vector
- Network
- Complexity
- Medium
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
Raw vector
AV:N/AC:M/Au:N/C:N/I:P/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2011-4451.md and follow it. Check whether this project is affected by CVE-2011-4451. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
