LiveActive security incident?Get immediate response
CVE Record

CVE-2023-49858: WordPress Custom Login plugin <= 4.1.0 - Broken Access Control vulnerability

Missing Authorization vulnerability in Austin Custom Login custom-login allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Custom Login: from n/a through <= 4.1.0.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-49858 is a broken access control issue in the WordPress Custom Login plugin up to version 4.1.0. An authenticated user may be able to perform an action that should require stronger authorization. The published score is medium, with low integrity impact and no reported confidentiality or availability impact.

Executive priority

Treat this as a moderate WordPress hygiene issue, not an emergency based on the provided evidence. Prioritize sites with public registration, many users, or sensitive branding/login workflows. Remediate during the next plugin maintenance cycle unless local exposure is unusually broad.

Technical view

The issue is described as CWE-862 Missing Authorization in Austin Custom Login custom-login through 4.1.0. CVSS 3.1 is 4.3: network reachable, low complexity, low privileges required, no user interaction, unchanged scope, low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites that have the Custom Login plugin installed at version 4.1.0 or earlier. The CVSS vector requires an authenticated low-privileged user, so sites with open registration or many contributor-level accounts may face higher practical risk.

Exploitation context

The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The vulnerability is not described as unauthenticated or remote code execution. Practical impact appears to depend on what unauthorized plugin action is reachable by low-privileged users.

Researcher notes

Available details are sparse: the bundle identifies missing authorization but not the exact protected action, endpoint, or fixed version. Avoid assuming exploitability beyond authenticated low-privileged integrity impact. Validation should focus on asset/version exposure and vendor advisory follow-up.

Mitigation direction

  • Inventory WordPress sites for the custom-login plugin and installed version.
  • Check vendor or Patchstack guidance for a fixed version or official mitigation.
  • Upgrade if an official fixed release is available from a trusted source.
  • Disable or remove the plugin where no fix is available and business impact allows.
  • Limit low-privileged WordPress accounts, especially on sites with public registration.

Validation and detection

  • Confirm whether Custom Login is installed on each WordPress site.
  • Record plugin versions and flag 4.1.0 or earlier for review.
  • Review WordPress user registration and role assignment settings.
  • Check administrative logs for unexpected Custom Login configuration changes.
  • Track remediation status against vendor or Patchstack advisories.
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-2023-49858 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-2023-49858Attack 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
AustinCustom Logincustom-login, 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.