Jobmonster - Job Board WordPress Theme <= 4.8.1 - Authentication Bypass
Strategic Overview
- Status
- Patched in 4.8.2
- Affected Theme
- Noo JobMonster
- Affected Version
<= 4.8.1- CVSS
- 9.8Critical
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2025-5397
At a glance
CVE-2025-5397 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Noo JobMonster WordPress theme, affecting versions <= 4.8.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.8.2; sites on affected versions should update now. Disclosed October 2025, reported by Thái An.
Vulnerability Overview
The Noo JobMonster theme for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 4.8.1. This is due to the check_login() function not properly verifying a user's identity prior to successfully authenticating them This makes it possible for unauthenticated attackers to bypass standard authentication and access administrative user accounts. Please note social login needs to be enabled in order for a site to be impacted by this vulnerability.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-288: Authentication Bypass Using an Alternate Path or Channel
Noo JobMonster <= 4.8.1 carries this weakness at check_login(), and reaching it takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For Noo JobMonster the fix is 4.8.2: builds <= 4.8.1 are affected, anything from 4.8.2 onward is not.
Remediation
Update to version 4.8.2, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Noo JobMonster 4.8.2 closes this, and updating the theme is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Noo JobMonster
- 9.8CVE-2024-37927: Jobmonster <= 4.7.5 Privilege Escalation
CVE-2024-37927 - 9.1CVE-2024-37928: Jobmonster < 4.7.5 Arbitrary File Deletion
CVE-2024-37928 - 7.5CVE-2026-25340: Noo JobMonster < 4.8.4 SQL Injection
CVE-2026-25340 - 7.5CVE-2025-67522: Jobmonster <= 4.8.2 Local File Inclusion
CVE-2025-67522 - 6.4CVE-2025-57887: Jobmonster <= 4.8.0 Stored Cross-Site Scripting
CVE-2025-57887 - 6.1CVE-2026-57368: Noo JobMonster <= 4.8.5 Reflected Cross-Site Scripting
CVE-2026-57368 - 6.1CVE-2025-54737: Jobmonster <= 4.7.8 Reflected Cross-Site Scripting
CVE-2025-54737 - 6.1CVE-2025-53201: Jobmonster <= 4.7.8 Reflected Cross-Site Scripting
CVE-2025-53201
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C