Apache Jspwiki vulnerabilities
29 CVEs affecting Apache Jspwiki, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-48910, published 2026-07-30.
More from Apache.
Highest priority
Known exploited (CISA KEV) first, then by EPSS exploit probability.
- CVE-2022-28730, published 2022-08-04. Medium severity, CVSS 6.1. EPSS: 85.8% chance of exploitation in the next 30 days. A carefully crafted request on AJAXPreview.jsp could trigger an XSS vulnerability on Apache JSPWiki, which could allow the attacker to execute javascript in the victim's browser and get some…
- CVE-2022-27166, published 2022-08-04. Medium severity, CVSS 6.1. EPSS: 85.8% chance of exploitation in the next 30 days. A carefully crafted request on XHRHtml2Markup.jsp could trigger an XSS vulnerability on Apache JSPWiki up to and including 2.11.2, which could allow the attacker to execute javascript in the victim's…
- CVE-2022-28732, published 2022-08-04. Medium severity, CVSS 6.1. EPSS: 82.4% chance of exploitation in the next 30 days. A carefully crafted request on WeblogPlugin could trigger an XSS vulnerability on Apache JSPWiki, which could allow the attacker to execute javascript in the victim's browser and get some sensitive…
- CVE-2024-27136, published 2024-06-24. Medium severity, CVSS 6.1. EPSS: 60.8% chance of exploitation in the next 30 days. XSS in Upload page in Apache JSPWiki 2.12.1 and priors allows the attacker to execute javascript in the victim's browser and get some sensitive information about the victim. Apache JSPWiki users…
- CVE-2022-28731, published 2022-08-04. Medium severity, CVSS 6.5. EPSS: 57.8% chance of exploitation in the next 30 days. A carefully crafted request on UserPreferences.jsp could trigger an CSRF vulnerability on Apache JSPWiki before 2.11.3, which could allow the attacker to modify the email associated with the attacked…
- CVE-2019-0225, published 2019-03-28. High severity, CVSS 7.5. EPSS: 10% chance of exploitation in the next 30 days. A specially crafted url could be used to access files under the ROOT directory of the application on Apache JSPWiki 2.9.0 to 2.11.0.M2, which could be used by an attacker to obtain registered users'…
- CVE-2021-44140, published 2021-11-24. Critical severity, CVSS 9.1. EPSS: 6.4% chance of exploitation in the next 30 days. Remote attackers may delete arbitrary files in a system hosting a JSPWiki instance, versions up to 2.11.0.M8, by using a carefuly crafted http request on logout, given that those files are reachable…
- CVE-2018-20242, published 2019-02-11. Medium severity, CVSS 6.1. EPSS: 5.4% chance of exploitation in the next 30 days. A carefully crafted URL could trigger an XSS vulnerability on Apache JSPWiki, from versions up to 2.10.5, which could lead to session hijacking.
- CVE-2019-0224, published 2019-03-28. Medium severity, CVSS 6.1. EPSS: 5.2% chance of exploitation in the next 30 days. In Apache JSPWiki 2.9.0 to 2.11.0.M2, a carefully crafted URL could execute javascript on another user's session. No information could be saved on the server or jspwiki database, nor would an…
- CVE-2019-10078, published 2019-05-20. Medium severity, CVSS 6.1. EPSS: 4.9% chance of exploitation in the next 30 days. A carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking. Initial reporting indicated…
Latest
- CVE-2026-48910, published 2026-07-30. Medium severity, CVSS 6.5. EPSS: 0.6% chance of exploitation in the next 30 days. A carefully crafted editing request could trigger an XSS vulnerability on Apache JSPWiki when parsing errors on the markdown renderer, which could allow the attacker to execute javascript in the…
- CVE-2026-28814, published 2026-07-30. High severity, CVSS 7.5. EPSS: 0.7% chance of exploitation in the next 30 days. Arbitrary Wiki Markup rendering due to lack of authentication in Apache JSPWiki up to 2.12.3 allows attacker to obtain sensitive data stored in JSPWiki variables. Users are recommended to upgrade to…
- CVE-2026-28813, published 2026-07-30. High severity, CVSS 8.8. EPSS: 0.3% chance of exploitation in the next 30 days. Apache JSPWiki, up to 2.12.3, is vulnerable to JSON Hijacking, which leads to csrf vulnerabilities. Users are recommended to upgrade to version 2.12.4, which fixes this issue.
- CVE-2026-28812, published 2026-07-30. Critical severity, CVSS 9.8. EPSS: 0.7% chance of exploitation in the next 30 days. UserManager lack of checks allows impersonation in Apache JSPWiki up to 2.12.3 which may allow attackers to escalate privileges. Users are recommended to upgrade to version 2.12.4 or newer which…
- CVE-2026-28811, published 2026-07-30. High severity, CVSS 7.5. EPSS: 0.8% chance of exploitation in the next 30 days. Debug Messages Revealing Unnecessary Information in Apache JSPWiki up to 2.12.3. Users are recommended to upgrade to version 2.12.4, which fixes this issue.
- CVE-2025-24854, published 2025-07-31. Medium severity, CVSS 6.1. EPSS: 0.4% chance of exploitation in the next 30 days. A carefully crafted request using the Image plugin could trigger an XSS vulnerability on Apache JSPWiki, which could allow the attacker to execute javascript in the victim's browser and get some…
- CVE-2025-24853, published 2025-07-31. High severity, CVSS 7.5. EPSS: 0.5% chance of exploitation in the next 30 days. A carefully crafted request when creating a header link using the wiki markup syntax, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information…
- CVE-2022-46907, published 2023-05-25. Medium severity, CVSS 6.1. EPSS: 1.2% chance of exploitation in the next 30 days. A carefully crafted request on several JSPWiki plugins could trigger an XSS vulnerability on Apache JSPWiki, which could allow the attacker to execute javascript in the victim's browser and get some…
- CVE-2022-34158, published 2022-08-04. High severity, CVSS 8.8. EPSS: 1.2% chance of exploitation in the next 30 days. A carefully crafted invocation on the Image plugin could trigger an CSRF vulnerability on Apache JSPWiki before 2.11.3, which could allow a group privilege escalation of the attacker's account.…