CVE-2025-14609
Unknown Unknown - Not Provided
Missing Authorization in Wise Analytics Plugin Exposes Sensitive Data

Publication date: 2026-01-24

Last updated on: 2026-04-08

Assigner: Wordfence

Description
The Wise Analytics plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.1.9. This is due to missing capability checks on the REST API endpoint '/wise-analytics/v1/report'. This makes it possible for unauthenticated attackers to access sensitive analytics data including administrator usernames, login timestamps, visitor tracking information, and business intelligence data via the 'name' parameter granted they can send unauthenticated requests.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-24
Last Modified
2026-04-08
Generated
2026-06-16
AI Q&A
2026-01-24
EPSS Evaluated
2026-06-15
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wordfence wise_analytics to 1.1.9 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in the Wise Analytics WordPress plugin (up to version 1.1.9) is due to missing authorization checks on the REST API endpoint '/wise-analytics/v1/report'. The endpoint's permission callback always returns true, meaning it does not enforce any access control. As a result, unauthenticated attackers can send requests to this endpoint and access sensitive analytics data such as administrator usernames, login timestamps, visitor tracking information, and business intelligence data by specifying the 'name' parameter in their requests. [1, 2]

Impact Analysis

This vulnerability can impact you by allowing unauthenticated attackers to access sensitive analytics data without any restrictions. This includes administrator usernames, login timestamps, visitor tracking details, and business intelligence data. Such unauthorized access can lead to privacy breaches, exposure of sensitive operational information, and potential further exploitation of your WordPress site or business intelligence assets. [1, 2]

Detection Guidance

You can detect this vulnerability by sending unauthenticated GET requests to the REST API endpoint '/wise-analytics/v1/report' on your WordPress site and checking if sensitive analytics data is returned without authentication. For example, you can use curl commands like: curl -X GET 'https://yourwordpresssite.com/wp-json/wise-analytics/v1/report?name=overview.highlights' or curl -X GET 'https://yourwordpresssite.com/wp-json/wise-analytics/v1/report?name=combined&reports=pages,visitors'. If these requests return data without requiring authentication, the vulnerability is present. [1, 2]

Mitigation Strategies

Immediate mitigation steps include disabling or removing the Wise Analytics plugin until a patched version is available, restricting access to the REST API endpoint '/wise-analytics/v1/report' via web server rules or firewall to block unauthenticated requests, and monitoring your WordPress site for unauthorized access. Applying updates from the plugin developer that implement proper permission checks on the REST API endpoint is essential once available. [1, 2]

Compliance Impact

The vulnerability allows unauthenticated attackers to access sensitive analytics data, including administrator usernames, login timestamps, visitor tracking information, and business intelligence data. This unauthorized disclosure of sensitive personal and business data could lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require proper access controls and protection of personal and sensitive information. Therefore, the missing authorization in the Wise Analytics plugin's REST API endpoint may result in violations of these standards due to exposure of protected data without consent or proper safeguards. [1, 2]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-14609. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart