LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40488: ProcessWire v3.0.200 was discovered to contain a Cross-Site Request Forgery (CSRF).

ProcessWire v3.0.200 was discovered to contain a Cross-Site Request Forgery (CSRF).

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-40488 is a reported CSRF flaw in ProcessWire v3.0.200. If a user can be tricked into interacting with malicious content, their browser may perform an unintended action in ProcessWire. The public metadata does not identify a patched version, endpoint, or confirmed exploitation.

Executive priority

Treat as a moderate-priority web application integrity issue. Prioritize confirmation of ProcessWire v3.0.200 exposure, then follow vendor guidance. Escalate if the affected instance supports sensitive administrative or business-changing workflows.

Technical view

The CVSS 3.1 vector is 6.5 medium: network exploitable, low complexity, no attacker privileges, user interaction required, unchanged scope, high integrity impact, and no confidentiality or availability impact. The issue is classified as CWE-352 Cross-Site Request Forgery. Provided sources do not describe the vulnerable request path or action.

Likely exposure

Exposure appears limited to environments running ProcessWire v3.0.200. The CVE record does not provide CPEs, vendor metadata, or affected-version ranges beyond that version, so broader exposure cannot be confirmed from the supplied sources.

Exploitation context

There is no KEV listing and no supplied source confirms active exploitation. The CVSS vector indicates exploitation requires user interaction, consistent with CSRF risk where a targeted user is induced to trigger an unwanted state-changing request.

Researcher notes

The evidence is sparse. The supplied CVE data establishes CSRF in ProcessWire v3.0.200 with CWE-352 and CVSS 6.5, but does not provide endpoint details, exploit maturity, affected ranges, or patch identification. Avoid assuming impact beyond unauthorized integrity changes.

Mitigation direction

  • Identify any ProcessWire v3.0.200 deployments in production or staging.
  • Check ProcessWire vendor guidance for fixed versions or recommended mitigations.
  • Upgrade if vendor release notes identify a corrected version.
  • Review state-changing forms for CSRF token and origin protections.
  • Limit access to sensitive ProcessWire functions where operationally possible.

Validation and detection

  • Inventory ProcessWire versions across web assets and hosted applications.
  • Confirm whether any running instance is exactly v3.0.200.
  • Review vendor changelogs or advisories for CVE-2022-40488 coverage.
  • Validate CSRF protections using authorized, non-destructive internal testing.
  • Review recent administrative changes for unexpected state changes.
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-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-40488 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
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.