LiveActive security incident?Get immediate response
CVE Record

CVE-2024-1649: Categorify <= 1.0.7.4 - Missing Authorization in categorifyAjaxDeleteCategory

The Categorify plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the categorifyAjaxDeleteCategory function in all versions up to, and including, 1.0.7.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete categories.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-1649 lets a logged-in low-privilege WordPress user delete Categorify categories because the plugin did not properly check authorization. This is not a full site takeover in the cited sources, but it can disrupt media organization and damage content workflows.

Executive priority

Treat this as a moderate-priority WordPress integrity issue. It should be fixed in normal vulnerability remediation cycles, faster for sites with public registration or many low-trust authenticated users.

Technical view

Categorify for WordPress is affected through version 1.0.7.4 by CWE-862 missing authorization in categorifyAjaxDeleteCategory. The reported impact is unauthorized category deletion by authenticated users with subscriber-level access or higher. CVSS 3.1 is 4.3, network exploitable, low complexity, low privileges, no user interaction.

Likely exposure

Exposure is limited to WordPress sites running Categorify versions up to and including 1.0.7.4, where untrusted users can authenticate as subscribers or above. Sites without this plugin or without low-trust accounts are less exposed based on the cited evidence.

Exploitation context

The source bundle does not show active exploitation, and CISA KEV status is false. The issue is still practical because it requires only authenticated subscriber-level access, which may be available on membership, customer, contributor, or publicly registered WordPress sites.

Researcher notes

Evidence supports missing authorization, not confidentiality loss, code execution, or active exploitation. The provided affected data is sparse, so version validation should rely on local plugin inventory and vendor changelog or WordPress.org changeset review.

Mitigation direction

  • Inventory WordPress sites for Categorify and record installed versions.
  • Check vendor guidance or plugin changelog for the authorization fix before upgrading.
  • Upgrade Categorify to a fixed release when confirmed by vendor sources.
  • Limit or disable untrusted subscriber-level account creation where possible.
  • Back up and monitor media category structures for unauthorized deletion.

Validation and detection

  • Confirm whether Categorify is installed and version is 1.0.7.4 or earlier.
  • Review user registration and subscriber access on affected WordPress sites.
  • Review logs or audit trails for category deletions by low-privilege users.
  • Confirm categorifyAjaxDeleteCategory now enforces an appropriate capability check.
  • Re-test business workflows that depend on media categories after remediation.
Prepared
Confidence
high
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-2024-1649 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:L/UI:N/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
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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/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-1649Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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
frenifyCategorify – WordPress Media Library Category & File Manager0unaffected
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.