LiveActive security incident?Get immediate response
CVE Record

CVE-2022-38140: WordPress SEO Plugin by Squirrly SEO Plugin <= 12.1.10 is vulnerable to Arbitrary File Upload

Auth. (contributor+) Arbitrary File Upload in SEO Plugin by Squirrly SEO plugin <= 12.1.10 on WordPress.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A WordPress SEO plugin from Squirrly had an authenticated arbitrary file upload issue in versions up to 12.1.10. A contributor-level user or higher could upload files in a way the application should not allow. This is high risk for multi-author WordPress sites, but the provided sources do not show active exploitation.

Executive priority

Prioritize assessment for public or multi-author WordPress sites using Squirrly SEO. The business urgency is high where untrusted contributors exist, but available evidence does not justify claiming active exploitation or a specific emergency patch version.

Technical view

CVE-2022-38140 is CWE-434 in SEO Plugin by Squirrly SEO for WordPress <= 12.1.10. CVSS 3.1 is 7.6: network exploitable, low complexity, low privileges, no user interaction, unchanged scope, with low confidentiality, high integrity, and low availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running SEO Plugin by Squirrly SEO at version 12.1.10 or earlier, where attacker-controlled contributor-or-higher accounts exist. Sites without the plugin, or without such accounts, are not shown as exposed by the provided sources.

Exploitation context

The source bundle marks this as not in KEV and provides no evidence of active exploitation. The vulnerability requires authenticated contributor-level or higher access. No exploit details, vulnerable endpoint, proof of concept, or weaponized activity are included in the supplied evidence.

Researcher notes

The available evidence identifies arbitrary file upload only at a summary level. It does not include vulnerable code paths, exploit conditions beyond contributor+ authentication, fixed version, or remediation details. Validate exposure through inventory and account review, then follow vendor or Patchstack guidance.

Mitigation direction

  • Identify all WordPress sites using Squirrly SEO.
  • Check plugin versions against the <= 12.1.10 affected range.
  • Review vendor and Patchstack guidance for fixed-version or mitigation details.
  • Restrict contributor-or-higher accounts to trusted users only.
  • Disable or remove the plugin where risk cannot be accepted.

Validation and detection

  • Confirm whether Squirrly SEO is installed on each WordPress site.
  • Record the exact installed plugin version.
  • Review contributor, author, editor, and administrator accounts.
  • Inspect recent uploaded files for unexpected or unauthorized content.
  • Check WordPress and hosting logs for suspicious authenticated upload activity.
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-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell 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-38140 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
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/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
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
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L2.84.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2022-38140Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/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
SquirrlySEO Plugin by Squirrly SEO (WordPress plugin)n/aunaffected
Weakness

CWE details

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

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.