CVE-2026-49083
Description
LatePoint plugin <=5.5.1 allows contributor-level users to escalate privileges, potentially leading to full site compromise.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
LatePoint plugin <=5.5.1 allows contributor-level users to escalate privileges, potentially leading to full site compromise.
Vulnerability
The LatePoint WordPress plugin, version 5.5.1 and earlier, contains a privilege escalation vulnerability that allows a user with a contributor-level account to escalate their privileges to a higher level. This issue arises from insufficient access control checks in the plugin's code, enabling lower-privileged users to perform actions reserved for higher roles [1].
Exploitation
An attacker must have a valid contributor-level account on a WordPress site running an affected version of LatePoint. No other special network position or user interaction is required; the attacker can directly exploit the vulnerability through normal authenticated requests to escalate their privileges [1].
Impact
Successful exploitation allows the attacker to gain elevated privileges, potentially up to administrator level. With higher privileges, the attacker can take full control of the website, including modifying content, installing malicious plugins, creating new admin accounts, and exfiltrating sensitive data. This leads to a complete compromise of the site's confidentiality, integrity, and availability [1].
Mitigation
Update to LatePoint version 5.5.2 or later, which resolves the vulnerability. Patchstack has also provided a mitigation rule that blocks attack attempts until the update is applied. Users are advised to apply the update immediately; if unable, enable auto-updates for vulnerable plugins through Patchstack [1].
AI Insight generated on Jun 15, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2<=5.5.1+ 1 more
- (no CPE)range: <=5.5.1
- (no CPE)range: <=5.5.1
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
1- Wordfence Intelligence Weekly WordPress Vulnerability Report (June 1, 2026 to June 7, 2026)Wordfence Blog · Jun 11, 2026