LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0572: WebPurify Profanity Filter <= 4.0.2 - Missing Authorization to Unauthenticated Plugin Settings Change via webpurify_save_options

The WebPurify Profanity Filter plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'webpurify_save_options' function in all versions up to, and including, 4.0.2. This makes it possible for unauthenticated attackers to change plugin settings.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-0572 lets unauthenticated internet users change settings in the WebPurify Profanity Filter WordPress plugin through a missing authorization check. This could disrupt moderation behavior or alter filtering configuration, but the cited CVSS indicates limited integrity and availability impact, with no confidentiality impact.

Executive priority

Treat as a medium-priority remediation item. It is not reported as actively exploited in the provided sources, but unauthenticated settings changes on public WordPress sites can create business and moderation risk. Prioritize internet-facing sites and high-traffic properties.

Technical view

The vulnerability is CWE-862, missing authorization, in the webpurify_save_options function. Wordfence reports all WebPurify Profanity Filter versions up to and including 4.0.2 are affected. The CVSS 3.1 score is 6.5, network exploitable, low complexity, no privileges, no user interaction, with low integrity and availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running the WebPurify Profanity Filter plugin at version 4.0.2 or earlier, especially where the site is internet-accessible. Sites not using this plugin are not affected based on the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The vulnerability is remotely reachable and unauthenticated, which increases practical risk, but impact appears limited to changing plugin settings rather than full site compromise.

Researcher notes

Evidence supports missing authorization on webpurify_save_options, but the source bundle does not identify a specific patched version or vendor mitigation. Avoid assuming broader WordPress compromise. Focus validation on plugin inventory, affected version confirmation, settings integrity, and vendor advisory tracking.

Mitigation direction

  • Identify WordPress sites using WebPurify Profanity Filter.
  • Check whether installed versions are 4.0.2 or earlier.
  • Review Wordfence and vendor/plugin repository guidance for a fixed release.
  • Update if a fixed version is available from trusted sources.
  • Disable or remove the plugin if no fix is available and risk is unacceptable.
  • Review plugin settings for unauthorized or unexpected changes.

Validation and detection

  • Confirm plugin presence and installed version in WordPress administration.
  • Compare findings against the affected range: up to and including 4.0.2.
  • Verify plugin settings match approved moderation configuration.
  • Review web and application logs for unexpected plugin settings changes.
  • Document whether a vendor-supported fixed version is available.
Prepared
Confidence
medium
Sources
4

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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-2026-0572 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
3Source 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-2026-0572Attack 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
webpurifyWebPurify Profanity Filter0unaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.