LiveActive security incident?Get immediate response
CVE Record

CVE-2022-44595: WordPress WP2FA plugin <= 2.2.0 - Broken Authentication vulnerability

Improper Authentication vulnerability in Melapress WP 2FA allows Authentication Bypass.This issue affects WP 2FA: from n/a through 2.2.0.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-44595 is a broken authentication issue in the Melapress WP 2FA WordPress plugin through version 2.2.0. The published impact is authentication bypass with limited confidentiality exposure. It matters most for WordPress sites relying on this plugin for two-factor authentication.

Executive priority

Treat as a moderate-priority WordPress authentication control issue. Prioritize sites where WP 2FA protects administrator or customer-facing accounts, but do not classify it as known exploited based on the provided evidence.

Technical view

The CVE describes CWE-287 improper authentication in WP 2FA through 2.2.0. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure is limited to WordPress installations using the Melapress WP 2FA plugin at version 2.2.0 or earlier. The source bundle does not identify affected CPEs or hosting environments.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The CVSS vector indicates a remote unauthenticated attack surface, but the bundle does not provide exploit details.

Researcher notes

Evidence is limited to the CVE record, CVE List entry, and Patchstack advisory reference. The bundle names authentication bypass but does not include exploit mechanics, fixed-version details, or observed exploitation.

Mitigation direction

  • Inventory WordPress sites for the wp-2fa plugin and installed version.
  • Check Melapress or Patchstack guidance for the vendor-confirmed fixed release.
  • Upgrade or replace vulnerable plugin versions according to vendor guidance.
  • If no safe update is available, assess disabling the plugin until remediated.
  • Review authentication monitoring for unexpected account access.

Validation and detection

  • Confirm whether WP 2FA is installed on each WordPress site.
  • Verify no site runs WP 2FA version 2.2.0 or earlier.
  • Compare findings against the CVE and Patchstack advisory.
  • After remediation, record the installed plugin version and date.
  • Review login records for anomalies during the exposure window.
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-287: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-44595 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
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2022-44595Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
MelapressWP 2FAwp-2fa, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-287 · source CWE mapping

Improper Authentication

Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.