LiveActive security incident?Get immediate response
CVE Record

CVE-2024-12296: Apus Framework <= 2.4 - Authenticated (Subscriber+) Arbitrary Options Update in import_page_options

The Apus Framework plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the 'import_page_options' function in all versions up to, and including, 2.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site. NOTE: This vulnerability was partially fixed in version 2.4.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-12296 lets any logged-in WordPress user at Subscriber level or higher change sensitive site options in Apus Framework. Those option changes can enable administrator account creation, turning a low-privilege account into full site control. The bundle says version 2.4 only partially fixed the issue, so remediation status is incomplete.

Executive priority

Treat this as high priority for WordPress sites with Apus Framework, especially public-registration sites. A basic user account may become an administrator. Prioritize inventory, access restriction, and vendor fix tracking before routine maintenance windows.

Technical view

Apus Framework for WordPress is missing a capability check in import_page_options through version 2.4. Authenticated low-privilege users can update arbitrary WordPress options. The CVSS 3.1 score is 8.8, with low complexity, network access, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

WordPress sites using Apus Framework versions up to and including 2.4 are the relevant exposure. Risk is higher where untrusted users can register or hold Subscriber-level accounts. The bundle does not prove exposure for other products beyond the named plugin.

Exploitation context

The source bundle does not cite CISA KEV listing or active exploitation. Exploitation requires authenticated Subscriber-level access or higher, but no user interaction. The described impact is privilege escalation through unauthorized WordPress option changes.

Researcher notes

The core issue is CWE-862: missing authorization around import_page_options. Evidence supports arbitrary option update and potential privilege escalation. Patch status is ambiguous because 2.4 is described as only a partial fix, and the bundle does not name a fully fixed release.

Mitigation direction

  • Check vendor and Wordfence guidance for a complete fixed version.
  • Do not assume version 2.4 fully remediates the issue.
  • Disable Apus Framework if exposure cannot be accepted or mitigated.
  • Restrict public registration and remove unnecessary Subscriber-level accounts.
  • Review WordPress options and administrator accounts for unauthorized changes.

Validation and detection

  • Inventory WordPress sites for Apus Framework installation and version.
  • Flag Apus Framework versions up to and including 2.4.
  • Review whether untrusted users can authenticate as Subscriber or above.
  • Check for unexpected administrator users or registration setting changes.
  • Monitor CVE and vendor references for final remediation guidance.
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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-2024-12296 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2024-12296Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
ApusThemeApus Framework0unaffected
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.