LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41609: WordPress Better Messages plugin <= 1.9.10.68 - Server-Side Request Forgery (SSRF) vulnerability

Auth. (subscriber+) Server-Side Request Forgery (SSRF) vulnerability in Better Messages plugin 1.9.10.68 on WordPress.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-41609 affects the Better Messages WordPress plugin version 1.9.10.68 and earlier. A logged-in low-privilege user, such as a subscriber, may be able to make the site server send unintended requests. Business risk is moderate because exploitation requires an account but could expose internal services or sensitive request paths.

Executive priority

Treat as a moderate-priority WordPress exposure issue. Prioritize internet-facing, multi-user, or self-registration sites because authenticated low-privilege access is enough to reach the vulnerable condition.

Technical view

The issue is an authenticated server-side request forgery in WordPlus Better Messages for WordPress, mapped to CWE-918. The CVSS 3.1 score is 6.4 with network access, low complexity, low privileges, no user interaction, changed scope, and low confidentiality and integrity impact. The source bundle does not identify a fixed version.

Likely exposure

Exposure is likely on WordPress sites running Better Messages 1.9.10.68 or earlier, especially public sites allowing subscriber registration or broad low-privilege user access.

Exploitation context

The bundle says exploitation requires an authenticated subscriber-level user or higher. It does not cite public exploitation, and the CVE is not listed as CISA KEV in the provided data.

Researcher notes

Evidence is limited to the CVE record, Patchstack listing, and WordPress plugin reference. Do not assume unauthenticated exploitation, active exploitation, or a specific fixed version from the provided bundle alone.

Mitigation direction

  • Inventory WordPress sites using the Better Messages plugin.
  • Check vendor and Patchstack guidance for the fixed or recommended plugin version.
  • Upgrade beyond affected versions when a vendor-supported fix is confirmed.
  • Disable the plugin if it is not business-critical and cannot be patched.
  • Restrict unnecessary subscriber-level account creation and access.
  • Monitor WordPress server egress for unexpected internal or metadata-service requests.

Validation and detection

  • Confirm whether Better Messages is installed on each WordPress site.
  • Record installed plugin versions and flag any version <= 1.9.10.68.
  • Review whether subscriber-level users can access messaging features.
  • Check logs for unusual outbound requests initiated by the WordPress server.
  • Verify remediation by confirming the installed version is no longer affected.
Prepared
Confidence
medium
Sources
4

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-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material 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-41609 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
6.4 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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
WordPlusBetter Messages (WordPress plugin)<= 1.9.10.68Listed
Weakness

CWE details

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

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.