Security readout for executives and security teams
Plain-English summary
CVE-2024-51667 is a medium-severity access control flaw in the WordPress Paytium plugin through version 4.4.10. An authenticated user could access functionality or data they should not be authorized to reach. The reported impact is limited to confidentiality, not site takeover or service disruption.
Executive priority
Prioritize remediation for WordPress sites that process payments, allow customer logins, or have many contributors. This is not currently evidenced as actively exploited, but it affects access control in a payment-related plugin and should be handled in the next routine security maintenance window.
Technical view
The issue is CWE-862 Missing Authorization in paytiumsupport Paytium for WordPress, affecting versions up to and including 4.4.10. CVSS 3.1 is 4.3 with network access, low attack complexity, low privileges required, no user interaction, and low confidentiality impact. Sources do not describe the vulnerable endpoint or a confirmed fixed version.
Likely exposure
Exposure is limited to WordPress sites running the Paytium plugin version 4.4.10 or earlier. The CVSS vector indicates an attacker needs a low-privileged authenticated account, reducing broad internet-wide risk but increasing concern on sites with open registration, many users, or weak account controls.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. No public exploit details are included in the source bundle. Treat this as a practical authenticated access-control risk rather than an unauthenticated mass-exploitation emergency.
Researcher notes
Available public details are sparse. The CVE identifies missing authorization but does not provide affected functions, exploit conditions beyond PR:L, or a fixed version. Avoid assuming impact beyond low confidentiality exposure unless vendor or Patchstack details confirm more.
Mitigation direction
Identify all WordPress sites using the Paytium plugin.
Check vendor or Patchstack guidance for a fixed release.
Update Paytium if a fixed version is available.
Disable or remove Paytium where it is not business-critical.
Limit creation of low-privileged WordPress accounts.
Review user roles and remove unnecessary accounts.
Validation and detection
Confirm whether Paytium is installed on each WordPress site.
Record the installed Paytium version.
Flag any installation at version 4.4.10 or earlier.
Review whether public registration or customer accounts are enabled.
Monitor logs for unusual authenticated access patterns.
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.