LiveActive security incident?Get immediate response
CVE Record

CVE-2022-1912: Button Widget Smartsoft <= 1.0.1 - Cross-Site Request Forgery to Cross-Site Scripting

The Button Widget Smartsoft plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0.1. This is due to missing nonce validation on the smartsoftbutton_settings page. This makes it possible for unauthenticated attackers to update the plugins settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-1912 affects the WordPress Button Widget Smartsoft plugin through version 1.0.1. A malicious link could cause an authenticated site administrator to unknowingly change plugin settings and store malicious script. For affected websites, this creates a credible path to site compromise through admin-assisted cross-site scripting.

Executive priority

Treat as high priority where the plugin is present, especially on public WordPress sites. The business risk is website takeover or visitor/admin compromise after administrator interaction.

Technical view

The plugin’s smartsoftbutton_settings page lacks nonce validation, enabling CSRF. An unauthenticated attacker who induces an administrator action can update plugin settings and inject web scripts. The source bundle rates this high severity with CVSS 3.1 score 8.8 and CWE-352.

Likely exposure

Exposure is limited to WordPress sites running Button Widget Smartsoft versions up to and including 1.0.1. The bundle does not support broader product impact.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. Exploitation requires user interaction by a site administrator, such as following a malicious link while authenticated.

Researcher notes

Evidence identifies missing nonce validation in the settings page as the root cause. The affected-version data in the bundle is partially inconsistent, so rely on the narrative stating versions up to 1.0.1 while verifying against vendor records.

Mitigation direction

  • Inventory WordPress sites for Button Widget Smartsoft installations.
  • Check vendor or WordPress plugin guidance for a fixed release.
  • Disable or remove the plugin if no fixed version is available.
  • Restrict administrative access to trusted users and managed devices.
  • Review plugin settings for unexpected scripts or unauthorized changes.

Validation and detection

  • Confirm whether Button Widget Smartsoft is installed on each WordPress site.
  • Verify the installed plugin version is greater than 1.0.1 or otherwise remediated.
  • Inspect plugin settings for injected script content.
  • Review administrator activity and web logs for suspicious settings changes.
  • Document unaffected sites where the plugin is absent.
Prepared
Confidence
medium
Sources
5

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-1912 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
8.8 (3.1)
Known Exploited
No
Published

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

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
4Source 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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
smartsoftbuttonwidgetButton Widget Smartsoft0unaffected
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.