Security readout for executives and security teams
Plain-English summary
This is a CSRF issue in the WordPress Sort SearchResult By Title plugin version 10.0 and earlier. An attacker may be able to trick a user into causing an unintended state-changing action. The published impact is limited to integrity, with no confidentiality or availability impact stated.
Executive priority
Treat as a moderate hygiene issue for WordPress estates. Prioritize sites using this plugin, especially externally managed or high-change sites. It is not listed as actively exploited in the provided data, but unresolved CSRF can still cause unauthorized configuration changes.
Technical view
CVE-2023-45639 is CWE-352 affecting Codex-m Sort SearchResult By Title for WordPress, package sort-searchresult-by-title, <=10.0. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact only.
Likely exposure
Exposure is limited to WordPress installations running Sort SearchResult By Title version 10.0 or earlier. The provided sources do not identify affected endpoints, required victim role, or a fixed version, so asset inventory is the primary exposure check.
Exploitation context
The source bundle does not show CISA KEV status or active exploitation. Exploitation would require user interaction, consistent with CSRF. No exploit details, public attack procedure, or weaponized evidence is included in the provided sources.
Researcher notes
The public bundle is sparse: it names CSRF, affected plugin, <=10.0, CVSS, and Patchstack reference, but not the vulnerable action, nonce coverage, role requirements, or fixed version. Avoid assuming exploitability beyond user-interaction CSRF with low integrity impact.
Mitigation direction
- Inventory WordPress sites for the sort-searchresult-by-title plugin.
- Remove or disable the plugin where it is not business-critical.
- Check Patchstack and vendor guidance for any fixed release or workaround.
- Limit WordPress administrative access to trusted users only.
- Monitor for unexpected plugin or search-result configuration changes.
Validation and detection
- Confirm each WordPress site's installed plugin version.
- Flag Sort SearchResult By Title versions 10.0 or earlier.
- Review plugin changelog or vendor source for CSRF fixes before declaring remediation.
- Check admin activity logs for unexplained setting changes.
- Record evidence when no affected plugin is installed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2023-45639 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.