dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-6990

HIGH · 8.8 CVSS v3.1 Published 2025-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The kallyas theme for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.24.0 via the `TH_PhpCode` pagebuilder widget. This is due to the theme not restricting access to the code editor widget for non-administrators. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The kallyas WordPress theme includes a TH_PhpCode pagebuilder widget that allows users to write and execute PHP code. Due to missing access control restrictions, any authenticated user with Contributor-level access or higher can access this widget and execute arbitrary code on the server, leading to full remote code execution.

MitigationImmediately restrict the TH_PhpCode widget to administrator-level users only by adding proper capability checks, or temporarily disable the widget in the theme until a patched version is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm kallyas theme is installed
    Navigate to Appearance > Themes in the WordPress admin dashboard and verify the kallyas theme is active. Check the theme version by viewing the style.css file or theme details.
    Affected if kallyas theme is active on the WordPress site
  2. Check for TH_PhpCode widget presence
    Access the WordPress pagebuilder (often found in Page Builder settings or theme options). Look for a widget labeled TH_PhpCode or PhpCode in the available widget list.
    Affected if TH_PhpCode widget is visible and available in the pagebuilder
  3. Verify authenticated user role access
    Navigate to Users > All Users in the WordPress admin. Identify users with Contributor, Author, or Editor roles. Test whether these roles can access the pagebuilder/TH_PhpCode widget by logging in as a test Contributor user.
    Affected if Users with Contributor-level access or higher can access the pagebuilder interface containing TH_PhpCode
  4. Inspect user capability settings
    Review the kallyas theme settings for any access control or capability configuration related to the TH_PhpCode widget. Check if there are role-based restrictions defined.
    Affected if No capability check restricts TH_PhpCode to Administrator role only, or no restrictions are defined

If the kallyas theme is active and users with Contributor-level access or higher can access the TH_PhpCode widget in the pagebuilder, the environment is affected by CVE-2025-6990.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict the TH_PhpCode widget to administrator-level users only by adding proper capability checks, or temporarily disable the widget in the theme until a patched version is released.

Recommended fix Moderate confidence

Kallyas theme version > 4.24.0 (contact vendor for exact fixed release)

  1. 1. Navigate to your WordPress dashboard and go to Appearance > Themes
  2. 2. Locate the Kallyas theme in your installed themes
  3. 3. Check if an update is available for the Kallyas theme
  4. 4. If an update is available, update to the latest version (beyond 4.24.0)
  5. 5. After updating, verify the TH_PhpCode widget is either removed or properly restricted to administrator-level users only
  6. 6. Test to ensure Contributor-level users can no longer access PHP code execution functionality

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6990 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data