CVE-2025-26935
Path Traversal in Wpjobportal Wp Job Portal ≤ 2.2.8
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-26935 is a high-severity Path Traversal: '.../...//' (CWE-35) vulnerability in Wpjobportal Wp Job Portal. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-26935 is a path traversal vulnerability in the WP Job Portal plugin (wp-job-portal) for WordPress, specifically exploiting the '.../...//' sequence to enable PHP local file inclusion (LFI). This flaw affects all versions of the plugin up to and including 2.2.8, with no lower bound specified. Mapped to CWE-35 (Path Traversal) and CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), it carries a CVSS v3.1 base score of 7.5 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating high potential impact despite elevated exploitation complexity.
The vulnerability can be exploited remotely over the network by an attacker with low privileges, such as an authenticated user with subscriber-level access or equivalent. Exploitation requires high attack complexity, likely due to specific input conditions or plugin states, but needs no user interaction from victims. Successful attacks enable high-impact confidentiality, integrity, and availability violations through LFI, potentially allowing arbitrary local file reads or PHP code execution if sensitive files like configuration or web shells are targeted.
For mitigation details, refer to the Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/wp-job-portal/vulnerability/wordpress-wp-job-portal-plugin-2-2-8-local-file-inclusion-vulnerability?_s_id=cve, which documents the issue and likely recommends updating to a patched version beyond 2.2.8 or applying available defenses.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-5435
Vulnerability Data
Path Traversal: '.../...//' vulnerability in wpjobportal WP Job Portal wp-job-portal allows PHP Local File Inclusion.This issue affects WP Job Portal: from n/a through <= 2.2.8.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes path sequences so the traversal cannot be introduced or exploited.
Enforces information flow rules that stop unauthorized directory escapes via crafted paths.
Least privilege reduces the impact of any successful traversal by limiting accessible resources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and path sanitization that neutralize traversal sequences.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect path-traversal flaws before release.
Secure SDLC mandates input validation and path-handling controls that directly mitigate path traversal.
Application security requirements include rules for safe file-path construction and canonicalization.
Secure architecture principles require proper directory restrictions and input sanitization to prevent traversal.
Secure coding standards explicitly forbid unsafe path concatenation and mandate canonicalization routines.
Information access restriction limits file reachability but does not address the input-validation flaw itself.