CVE-2025-14358
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing Authorization vulnerability in sizam REHub Framework rehub-framework allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects REHub Framework: from n/a through <= 19.9.5.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMissing authorization vulnerability in REHub Framework (versions up to 19.9.5) allows unauthorized access to functionality that should be constrained by access control lists (ACLs). This is a CWE-862 type vulnerability where the application fails to verify user permissions before executing sensitive operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify REHub Framework installation and versionLocate the REHub theme folder in your WordPress installation (typically in /wp-content/themes/rehub-framework or /wp-content/themes/rehub) and check the style.css file for the 'Version:' header, or check the main plugin/theme PHP file for the version constant.Affected if The installed version is 19.9.5 or any earlier version (e.g., 19.9.0, 19.8.x, etc.) since the vulnerability affects versions up to 19.9.5.
-
Confirm REHub is the active themeCheck your WordPress admin dashboard under Appearance > Themes to verify which theme is currently active, or query the database wp_options table for the 'template' or 'stylesheet' option values.Affected if REHub Framework is the active theme and the version is within the affected range.
-
Identify sensitive functionality endpointsReview the REHub Framework code for functions that handle user data, content management, or privileged operations (typically found in includes/admin/, functions/ or class files). Look for AJAX handlers, admin pages, or public-facing submission forms.Affected if The codebase contains admin-level or privileged functions that do not include current_user_can() or similar authorization checks before executing.
-
Test for unauthorized access to restricted featuresUsing a low-privilege or unauthenticated user account, attempt to access or trigger suspected sensitive functions identified in step 3. This may include submitting requests to admin-ajax.php with action parameters, accessing direct URLs, or calling API endpoints.Affected if The restricted functionality executes or returns data without requiring proper user capability verification (HTTP 200 response with sensitive data or action completion).
You are affected if REHub Framework version 19.9.5 or earlier is installed as your active theme AND sensitive functionality can be accessed without proper authorization checks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper role-based access control (RBAC) checks on all sensitive functionality, ensuring that authorization is validated before any privileged operation executes. The specific vulnerable endpoints or functions require further investigation to apply targeted fixes.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14358 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data