LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4413: Process Steps Template Designer <= 1.2.1 - Cross-Site Request Forgery Bypass

The Process Steps Template Designer plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.2.1. This is due to missing or incorrect nonce validation on the save() function. This makes it possible for unauthenticated attackers to save field icons via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-4413 affects the Process Steps Template Designer WordPress plugin. A malicious site or link could cause a logged-in administrator to save field icon changes without proper request validation. The impact is limited integrity change, but it matters for sites using this plugin because administrator interaction is enough to trigger it.

Executive priority

Treat this as a moderate WordPress hygiene item, not an emergency. Prioritize remediation for public or business-critical sites using the plugin, then fold remaining instances into normal plugin patch management.

Technical view

The vulnerability is a CSRF issue in the plugin's save() function, attributed to missing or incorrect nonce validation. Sources identify versions up to and including 1.2.1 as vulnerable. The CVSS 3.1 score is 4.3, with network access, low complexity, no attacker privileges, required user interaction, and low integrity impact.

Likely exposure

Exposure is limited to WordPress sites running Process Steps Template Designer versions up to and including 1.2.1, especially where administrators are active in the dashboard. The bundle does not identify affected CPEs or broader product families.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. Abuse requires tricking a site administrator into taking an action such as clicking a link, after which a forged request could save field icons.

Researcher notes

The core issue is CWE-352 CSRF on save(), with integrity-only impact in the supplied CVSS vector. Evidence supports administrator-assisted exploitation but not standalone unauthenticated compromise or active exploitation. Fixed-version details are not explicit in the supplied bundle, so confirm against vendor or WordPress records.

Mitigation direction

  • Inventory WordPress sites for Process Steps Template Designer and record installed versions.
  • Update the plugin using official WordPress or vendor guidance if a fixed version is available.
  • Remove or disable the plugin where it is not required.
  • Limit administrator browsing from active WordPress sessions where practical.
  • Review plugin settings for unexpected field icon changes.

Validation and detection

  • Confirm whether any site runs Process Steps Template Designer version 1.2.1 or earlier.
  • Check the plugin changelog or WordPress Trac for nonce validation changes around save().
  • Verify administrative save actions require valid nonce protection in the installed version.
  • Review recent admin activity and plugin settings for unauthorized icon changes.
Prepared
Confidence
high
Sources
6

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-2021-4413 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
4.3 (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: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
0Timeline events
0ADP providers
10Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2021-4413Attack 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:N

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
narinder-singhProcess Steps Template Designer0unaffected
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.