LiveActive security incident?Get immediate response
CVE Record

CVE-2022-44737: WordPress All In One WP Security plugin <= 5.1.0 - Multiple Cross-Site Request Forgery (CSRF) vulnerabilities

Multiple Cross-Site Request Forgery vulnerabilities in All-In-One Security (AIOS) – Security and Firewall (WordPress plugin) <= 5.1.0 on WordPress.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites running the All-In-One Security (AIOS) plugin version 5.1.0 or older. The issue is multiple CSRF flaws, meaning an attacker may be able to cause an authenticated browser to perform unintended plugin actions. The CVSS score is 6.5, with limited integrity and availability impact and no confidentiality impact stated.

Executive priority

Treat this as a moderate-priority WordPress plugin maintenance issue. It does not have supplied evidence of active exploitation, but security plugins are sensitive control points, so outdated affected installations should be identified and updated promptly.

Technical view

CVE-2022-44737 is a CWE-352 CSRF issue in All-In-One Security (AIOS) – Security and Firewall for WordPress, reported for versions up to 5.1.0. The supplied CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L. Sources do not identify specific vulnerable endpoints, fixed version, or detailed remediation steps.

Likely exposure

Exposure is likely limited to WordPress deployments using the AIOS plugin at version 5.1.0 or earlier. Sites without this plugin, or with versions outside the affected range, are not indicated as affected by the supplied sources.

Exploitation context

The bundle does not show CISA KEV listing or cite active exploitation. CSRF risk generally depends on a victim browser having valid WordPress privileges and processing a forged request, but the sources do not provide exploit details or observed attack evidence.

Researcher notes

The public bundle confirms CSRF class, affected product, and <=5.1.0 scope, but lacks endpoint-level details, proof of exploitation, and fixed-version data. Avoid assuming broader AIOS versions or specific attack outcomes beyond low integrity and availability impact from the CVSS vector.

Mitigation direction

  • Inventory WordPress sites for the AIOS plugin and record installed versions.
  • Prioritize sites running AIOS 5.1.0 or earlier for remediation review.
  • Check vendor and Patchstack guidance for the confirmed fixed version.
  • Update the plugin through approved WordPress maintenance processes when guidance confirms a safe version.
  • Review administrative access and harden privileged WordPress accounts.

Validation and detection

  • Confirm whether each WordPress site has the AIOS plugin installed.
  • Verify the installed AIOS version is not 5.1.0 or older.
  • Check plugin changelog or vendor advisory for CSRF remediation confirmation.
  • Review WordPress logs for unexpected administrative plugin configuration changes.
  • Confirm normal site and security plugin behavior after updating.
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-44737 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:N/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
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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
All In One WP Security & Firewall TeamAll-In-One Security (AIOS) – Security and Firewall (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-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.