CVE-2025-23963: WordPress Mark Posts plugin <= 2.2.4 - Broken Access Control vulnerability
Missing Authorization vulnerability in flymke Mark Posts mark-posts allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Mark Posts: from n/a through <= 2.2.4.
Security readout for executives and security teams
Plain-English summary
This is a medium-risk WordPress plugin access-control issue. A logged-in user may be able to perform actions in the Mark Posts plugin that should require stronger authorization. The expected business impact is limited integrity and availability impact, not data theft, based on the supplied CVSS vector.
Executive priority
Prioritize normal patch management and account hygiene. Escalate only for sites where many untrusted users can log in or where post state changes affect operations, publishing workflows, or customer-facing content.
Technical view
CVE-2025-23963 affects flymke Mark Posts through version 2.2.4. The listed weakness is CWE-862, Missing Authorization. CVSS 3.1 is 5.4 with network access, low complexity, low privileges required, no user interaction, and low integrity and availability impact.
Likely exposure
Exposure is likely limited to WordPress sites running the Mark Posts plugin at affected versions through 2.2.4. The CVSS vector indicates attackers need a valid low-privilege account, so public anonymous exposure is not supported by the source bundle.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. No exploit details are provided. The main concern is abuse by authenticated users or compromised low-privilege WordPress accounts to change plugin-controlled state without proper authorization.
Researcher notes
The evidence supports missing authorization in Mark Posts, but does not provide exploit mechanics or a named fix. The bundle has minor version ambiguity because the CVE text says through 2.2.4 while the Patchstack URL references 2.2.3.
Mitigation direction
Inventory WordPress sites for the Mark Posts plugin and installed version.
Check vendor or Patchstack guidance for a fixed version or official remediation.
Disable Mark Posts where it is not business-critical until remediation is confirmed.
Reduce unnecessary WordPress user accounts and privileges on affected sites.
Monitor for unexpected post-marking changes or plugin-related permission anomalies.
Validation and detection
Confirm whether Mark Posts is installed on each WordPress site.
Record plugin versions and flag versions through 2.2.4 as affected.
Review WordPress users with access to affected sites, especially low-privilege accounts.
Check plugin and application logs for unexpected state changes.
Track the Patchstack and CVE entries for updated remediation details.
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-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.