Security readout for executives and security teams
Plain-English summary
CVE-2025-24622 is a CSRF flaw in the WordPress Job Board Manager plugin through version 2.1.59. An attacker may be able to trick a logged-in user into causing unintended changes. The source bundle does not identify the affected action or a confirmed fixed version.
Executive priority
Treat this as a moderate WordPress hygiene issue. It is not reported as actively exploited in the supplied sources, but exposed public sites should be identified and moved to vendor-confirmed safe versions promptly.
Technical view
The record maps this to CWE-352 with CVSS 3.1 score 5.4. The vector indicates network reachability, low attack complexity, required user interaction, and low integrity and availability impact. Evidence names PickPlugins Job Board Manager package job-board-manager through 2.1.59.
Likely exposure
Exposure is limited to WordPress sites running PickPlugins Job Board Manager version 2.1.59 or earlier. Sites without this plugin, or with versions confirmed unaffected by vendor guidance, are not indicated as exposed.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. CSRF generally depends on a victim interaction while the victim has a valid WordPress session. The exact vulnerable action and required user role are not provided.
Researcher notes
Evidence is thin. The CVE and Patchstack reference establish CSRF and affected versions, but not the endpoint, nonce failure, role requirement, exploit availability, or fixed version. Avoid assuming impact beyond low integrity and availability from CVSS.
Mitigation direction
Inventory WordPress sites for the Job Board Manager plugin and installed version.
If version is <=2.1.59, check vendor or Patchstack guidance for a fixed release.
Update the plugin after confirming the vendor-supported fixed version.
If no fix is available, consider disabling the plugin until guidance is published.
Limit administrative sessions and use least-privilege WordPress accounts.
Validation and detection
Confirm whether job-board-manager is installed on each WordPress site.
Record the plugin version and compare it with the <=2.1.59 affected range.
Review vendor, WordPress.org, or Patchstack guidance for remediation status.
Check access logs for unusual job-board management changes around user sessions.
Document whether the plugin is disabled, upgraded, or accepted as residual risk.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.