Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-28814 – Unauthenticated Sensitive Data Disclosure – Apache JSPWiki up to 2.12.3

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-28814 is a high-severity information disclosure vulnerability in Apache JSPWiki affecting all versions up to and including 2.12.3. Due to missing authentication on critical wiki markup rendering functionality (CWE-306), unauthenticated remote attackers can render arbitrary wiki markup and obtain sensitive data stored in JSPWiki variables. The vulnerability carries a CVSS v3.1 score of 7.5 (HIGH) and requires no credentials or user interaction to exploit.

Technical details

  • Root cause: Apache JSPWiki fails to enforce authentication before processing wiki markup rendering requests, classified as CWE-306 (Missing Authentication for Critical Function).
  • Trigger conditions: An unauthenticated attacker sends a crafted HTTP request to the wiki markup rendering endpoint — no credentials, no user interaction, and no complex preconditions are required.
  • Attack vector: Fully remote and network-accessible (CVSS AV:N, AC:L, PR:N, UI:N); any internet-facing JSPWiki instance is directly reachable by an attacker.
  • Impact: High confidentiality impact — attackers can extract sensitive data stored in JSPWiki’s internal variables (e.g., configuration values, system properties, or application-level data surfaced through wiki variable rendering). There is no integrity or availability impact.

Affected software

  • Apache JSPWiki — all versions from inception through 2.12.3 (inclusive)

Severity

  • CVSS v3.1 Base Score: 7.5 (HIGH)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate — upgrade: Update Apache JSPWiki to version 2.12.4 or 3.0.0, both of which contain the vendor-issued fix for this vulnerability.
  • If immediate patching is not feasible: Restrict network access to JSPWiki instances so that only trusted users and IP ranges can reach the application. Placing the instance behind an authenticated reverse proxy or WAF rule that blocks unauthenticated requests to markup rendering endpoints can reduce exposure while a maintenance window is scheduled.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge