CVE-2025-6991
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 · uneditedThe kallyas theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.21.0 via the 'TH_LatestPosts4` widget. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.
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 confidenceThe kallyas WordPress theme contains a Local File Inclusion vulnerability in the TH_LatestPosts4 widget affecting all versions up to 4.21.0. Authenticated attackers with Contributor-level access or higher can manipulate widget parameters to include and execute arbitrary .php files on the server, achieving arbitrary PHP code execution.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed kallyas theme versionNavigate to Appearance > Themes in WordPress admin dashboard to view the active theme version, or locate and read the style.css file in wp-content/themes/kallyas/ and find the Version: headerAffected if The theme version is 4.21.0 or lower (any version up to and including 4.21.0)
-
Confirm TH_LatestPosts4 widget presenceCheck WordPress admin at Appearance > Widgets for the TH_LatestPosts4 widget in any active sidebar, or search the wp_options database table for entries containing 'latestposts4' or 'th_latestposts4'Affected if The TH_LatestPosts4 widget is currently active in any widget area or was previously configured
-
Enumerate users with contributor-level access or higherGo to Users > All Users in WordPress admin and review the role column for any accounts with Contributor, Author, Editor, or Administrator roles, or query the wp_usermeta table for role metadataAffected if Any user account exists with Contributor, Author, Editor, or Administrator role
Environment is affected if kallyas theme version 4.21.0 or lower is installed, the TH_LatestPosts4 widget is present, and at least one user with Contributor-level or higher access exists on the site
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the kallyas theme to a version newer than 4.21.0. If no patch is available, disable the TH_LatestPosts4 widget, review server-side file inclusion protections, and limit contributor-level user permissions until a fix is released.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6991 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6991 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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