LiveActive security incident?Get immediate response
CVE Record

CVE-2022-46859: WordPress Spiffy Calendar Plugin <= 4.9.1 is vulnerable to SQL Injection

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Spiffy Plugins Spiffy Calendar spiffy-calendar allows SQL Injection.This issue affects Spiffy Calendar: from n/a through 4.9.1.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-46859 is a critical SQL injection issue in the WordPress Spiffy Calendar plugin through version 4.9.1. If exploited, it could let an attacker affect the site database, creating confidentiality, integrity, and availability risk for affected WordPress sites.

Executive priority

Treat this as urgent for any public WordPress site using Spiffy Calendar. The potential database impact is high, but urgency depends on confirmed plugin presence and whether the vulnerable functionality is reachable.

Technical view

The CVE describes CWE-89 improper neutralization of SQL special elements in Spiffy Plugins Spiffy Calendar. The bundled CVSS v3.1 score is 9.8 with network attack vector, low complexity, no user interaction, and high impact across confidentiality, integrity, and availability.

Likely exposure

Exposure is likely limited to WordPress sites with the Spiffy Calendar plugin installed at version 4.9.1 or earlier. The source bundle does not provide CPEs or a complete affected-version range beyond “through 4.9.1.”

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector says no privileges required, while the Patchstack URL text includes “auth”; verify advisory details before assuming unauthenticated exploitability.

Researcher notes

Evidence is sparse in the provided bundle. Key uncertainty is authentication context because the CVSS vector says PR:N, but the Patchstack reference text suggests authenticated SQL injection. Do not assume exploit status without additional vendor or KEV evidence.

Mitigation direction

  • Inventory WordPress sites for Spiffy Calendar plugin usage and versions.
  • Upgrade if vendor or Patchstack guidance identifies a fixed release beyond 4.9.1.
  • Disable or remove the plugin where it is not business-critical.
  • Check vendor guidance before relying on compensating controls.
  • Increase monitoring for database errors and suspicious WordPress requests.

Validation and detection

  • Confirm whether Spiffy Calendar is installed on each WordPress instance.
  • Record installed plugin version and flag 4.9.1 or earlier.
  • Review advisory details for authentication requirements and fixed-version availability.
  • Check logs for unusual calendar-related requests or database errors.
  • Verify remediation by confirming the plugin is 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-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-46859 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-46859Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
Spiffy PluginsSpiffy Calendarspiffy-calendar, n/aunaffected
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.