LiveActive security incident?Get immediate response
CVE Record

CVE-2024-33683: WordPress Hide Dashboard Notifications plugin <= 1.2.3 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in WP Republic Hide Dashboard Notifications.This issue affects Hide Dashboard Notifications: from n/a through 1.2.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the WordPress Hide Dashboard Notifications plugin through version 1.2.3. It is a CSRF issue, meaning an attacker may be able to trick a logged-in user into making an unintended change. The documented impact is limited integrity loss, not data theft or service outage.

Executive priority

Handle during the normal vulnerability remediation cycle, with faster action for business-critical WordPress sites. The impact appears limited, but affected public websites still need inventory, ownership, and a clear remediation decision.

Technical view

CVE-2024-33683 is a CWE-352 CSRF vulnerability in WP Republic Hide Dashboard Notifications, package wp-hide-backed-notices, through 1.2.3. CVSS 3.1 is 4.3 with network access, low complexity, no privileges, required user interaction, unchanged scope, and low integrity impact.

Likely exposure

Exposure is limited to WordPress sites running Hide Dashboard Notifications version 1.2.3 or earlier. The source bundle does not identify affected endpoints, configuration prerequisites, install prevalence, or a confirmed fixed version.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and the cited sources do not state active exploitation. Successful abuse requires user interaction, consistent with CSRF risk against a logged-in WordPress user.

Researcher notes

Source evidence identifies CSRF in WP Republic Hide Dashboard Notifications through 1.2.3 with CVSS 4.3. The bundle does not provide vulnerable request details, nonce behavior, proof of concept, fixed version, workaround, or active exploitation evidence.

Mitigation direction

  • Inventory WordPress sites for the Hide Dashboard Notifications plugin.
  • Confirm whether installed versions are 1.2.3 or earlier.
  • Check WP Republic and Patchstack guidance for a fixed release or official mitigation.
  • If no fixed release is available, disable or remove the plugin where feasible.
  • Prioritize sites with multiple administrators or high-value content workflows.

Validation and detection

  • Search WordPress plugin inventories for wp-hide-backed-notices.
  • Verify the installed Hide Dashboard Notifications version on each site.
  • Review WordPress admin activity for unexpected settings or notice-related changes.
  • Monitor the CVE and Patchstack records for updated remediation details.
  • Document whether the plugin is needed, updated, disabled, or removed.
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-2024-33683 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
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
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-2024-33683Attack 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
WP RepublicHide Dashboard Notificationswp-hide-backed-notices, 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.