LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24532: WordPress SiteLock Security plugin <= 5.0.2 - Broken Access Control vulnerability

Missing Authorization vulnerability in SiteLock SiteLock Security – WP Hardening, Login Security & Malware Scans sitelock allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SiteLock Security – WP Hardening, Login Security & Malware Scans: from n/a through <= 5.0.2.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24532 is a medium-severity access-control flaw in the WordPress SiteLock Security plugin through version 5.0.2. A logged-in user may be able to perform an action they should not be authorized to perform, causing limited integrity impact. There is no source-provided evidence of active exploitation.

Executive priority

Address during the normal vulnerability remediation cycle, faster for public sites with user accounts. Business impact appears limited, but access-control flaws can undermine trust if authenticated users modify data or settings beyond their role.

Technical view

The CVE describes CWE-862 Missing Authorization in SiteLock Security – WP Hardening, Login Security & Malware Scans, package name sitelock. CVSS 3.1 is 4.3: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites running the SiteLock Security plugin at version 5.0.2 or earlier. Exploitation requires an authenticated low-privilege account, reducing urgency versus unauthenticated flaws but still relevant for membership, ecommerce, or multi-user sites.

Exploitation context

The provided sources do not include exploit details, proof-of-concept availability, or active exploitation claims. CISA KEV status is false in the supplied data. Treat this as a practical authorization-risk issue where attacker access may come from compromised or low-privilege WordPress accounts.

Researcher notes

Evidence is sparse. The CVE and Patchstack reference identify the vulnerability class and affected version range but do not provide a named vulnerable endpoint, fixed release, or exploitation evidence in the supplied bundle. Avoid assuming broader impact beyond low-integrity authorization bypass.

Mitigation direction

  • Inventory WordPress sites for the SiteLock Security plugin and version.
  • Prioritize sites allowing user registration or multiple non-admin accounts.
  • Check SiteLock or WordPress plugin guidance for a fixed version or workaround.
  • Update or disable the plugin if vendor guidance recommends it.
  • Restrict untrusted user accounts until remediation is confirmed.

Validation and detection

  • Confirm whether the sitelock plugin is installed on each WordPress site.
  • Record installed plugin versions and compare against <= 5.0.2.
  • Review user roles and presence of low-privilege accounts.
  • Check vendor and Patchstack pages for updated remediation details.
  • After changes, verify the plugin version and site functionality.
Prepared
Confidence
medium
Sources
3

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24532 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-24532Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SiteLockSiteLock Security – WP Hardening, Login Security & Malware Scanssitelock, 0unaffected
Weakness

CWE details

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.