CVE-2025-63051

REHub Framework < 19.9.9.4 - Authenticated (Subscriber+) Information Exposure

2025-12-06 00:00
Ananda Dhakal

Strategic Overview

Status
Patched in 19.9.9.4
Affected Plugin
reHub Framework
Affected Version
< 19.9.9.4
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-63051
View all reHub Framework vulnerabilities

At a glance

CVE-2025-63051 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the reHub Framework WordPress plugin, affecting versions < 19.9.9.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 19.9.9.4; sites on affected versions should update now. Disclosed December 2025, reported by Ananda Dhakal.

Vulnerability Overview

The reHub Framework plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and excluding, 19.9.9.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract sensitive user or configuration data.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in reHub Framework < 19.9.9.4 takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For reHub Framework the fix is 19.9.9.4: builds < 19.9.9.4 are affected, anything from 19.9.9.4 onward is not.

Remediation

Update to version 19.9.9.4, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: reHub Framework 19.9.9.4 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C