dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-12497

HIGH · 8.1 CVSS v3.1 Published 2025-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Premium Portfolio Features for Phlox theme plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.3.10 via the 'args[extra_template_path]' parameter. This makes it possible for unauthenticated attackers 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 confidence

The Premium Portfolio Features for Phlox WordPress plugin is vulnerable to unauthenticated Local File Inclusion via the 'args[extra_template_path]' parameter in all versions up to 2.3.10. Attackers can include and execute arbitrary .php files on the server, allowing complete code execution and potential bypass of access controls.

MitigationUpdate the Premium Portfolio Features for Phlox plugin to version 2.3.11 or later. Until patched, the site is vulnerable to remote code execution by any unauthenticated visitor.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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. Verify Premium Portfolio Features plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Premium Portfolio Features' or check the plugin directory (wp-content/plugins/) for a folder containing 'portfolio' or 'premium' in the name.
    Affected if The plugin is present in the WordPress installation.
  2. Check installed plugin version
    In WordPress admin, view the plugin details to see the version number, or read the main plugin PHP file (usually contains version definition in the header comment) in the plugin folder.
    Affected if The version number is 2.3.10 or lower.
  3. Identify if extra_template_path feature is accessible
    Examine if the plugin handles HTTP requests with the 'args[extra_template_path]' parameter. Check plugin files for code that processes this parameter, typically in ajax handlers or template inclusion functions.
    Affected if The plugin processes the 'extra_template_path' parameter from user input.
  4. Check server logs for exploitation attempts
    Review web server access logs (Apache/nginx) for requests containing 'extra_template_path' or path traversal sequences (../) targeting PHP files.
    Affected if Logs show requests with 'extra_template_path' parameter containing path traversal patterns.

The environment is affected if the Premium Portfolio Features plugin is installed with version 2.3.10 or lower and the extra_template_path parameter is processed by the application.

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

Update the Premium Portfolio Features for Phlox plugin to version 2.3.11 or later. Until patched, the site is vulnerable to remote code execution by any unauthenticated visitor.

Recommended fix Moderate confidence

Latest version on WordPress plugin repository (newer than 2.3.10)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Premium Portfolio Features for Phlox' (or 'auxin-portfolio') in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. If no update appears, check the WordPress plugin repository for the latest version and manually update
  6. 6. Verify the plugin is running a version newer than 2.3.10 after updating

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12497 — 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-12497 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