LiveActive security incident?Get immediate response
CVE Record

CVE-2022-38085: WordPress Read more By Adam plugin <= 1.1.8 - Cross-Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Read more By Adam plugin <= 1.1.8 at WordPress.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the Read more By Adam WordPress plugin through version 1.1.8. It is a CSRF issue, meaning an attacker may trick a logged-in user into triggering an unintended site action. The public bundle does not specify the exact action affected or a confirmed fixed version.

Executive priority

Treat as a moderate WordPress hygiene issue. Prioritize internet-facing business sites and administrator-heavy environments, but this is not supported as actively exploited or critical by the supplied evidence.

Technical view

CVE-2022-38085 is CWE-352 CSRF in Read more By Adam for WordPress, affecting versions <= 1.1.8. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, and low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites with the Read more By Adam plugin installed at version 1.1.8 or earlier. Sites without this plugin are not indicated as affected by the supplied sources.

Exploitation context

The bundle does not show CISA KEV listing or cited active exploitation. CSRF typically requires convincing a user with relevant site access to interact with attacker-controlled content. The source data does not include exploit details or affected request paths.

Researcher notes

The public bundle identifies the vulnerability class, affected version range, CVSS vector, and references. It does not provide endpoint-level detail, proof of concept, exploit status, or a named fixed version, so technical validation should rely on vendor or Patchstack updates.

Mitigation direction

  • Inventory WordPress sites for this plugin and version.
  • Review Patchstack and the WordPress plugin page for official remediation guidance.
  • Upgrade if a fixed version is available from the vendor.
  • Disable or remove the plugin if no safe version is confirmed.
  • Warn administrators to avoid untrusted links until remediated.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Record the active plugin version and compare it to <= 1.1.8.
  • Verify the vulnerable version is no longer active after remediation.
  • Review site change history for unexpected plugin-related changes.
  • Document unresolved sites and vendor guidance status.
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-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-2022-38085 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.4 (3.1)
Known Exploited
No
Published

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

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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
Adam SkaatRead more By Adam (WordPress plugin)<= 1.1.8Listed
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

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