dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-8905

MEDIUM · 6.3 CVSS v3.1 Published 2025-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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 Inpersttion For Theme plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.0 via the theme_section_shortcode() function. This is due to the plugin not restricting what functions can be called. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server which is limited to arbitrary functions without any user supplied parameters.

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 Inpersttion For Theme WordPress plugin (versions up to 1.0) contains an authenticated RCE vulnerability in the theme_section_shortcode() function. The shortcode does not restrict which PHP functions can be called, allowing authenticated attackers with Contributor-level access to execute arbitrary server-side functions without requiring user-supplied parameters.

MitigationUntil a patched version is released, disable or remove the plugin. If continued use is required, implement application-level restrictions on the shortcode or migrate to a secure alternative plugin.

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
Low
Integrity
Low
Availability
Low

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

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 plugin installation
    Check if the Impression For Theme plugin files exist in the WordPress plugins directory (wp-content/plugins/)
    Affected if The plugin directory 'impression-for-theme' or similar exists on the server
  2. Confirm plugin version
    Access the WordPress admin dashboard, navigate to Plugins, and check the installed version of Impression For Theme against the affected range (versions up to and including 1.0)
    Affected if The installed version is 1.0 or lower
  3. Identify active shortcode
    Search WordPress posts, pages, or widget content for the [theme_section] shortcode being used, or check the plugin source for registered shortcode handlers
    Affected if The [theme_section] shortcode is present and active on the site
  4. Review user roles
    Check WordPress user roles to identify accounts with Contributor-level access or higher privileges
    Affected if There are user accounts with Contributor, Author, Editor, or Administrator roles who could potentially exploit this vulnerability

A user is affected if the Impression For Theme plugin version 1.0 or lower is installed with the [theme_section] shortcode active and any Contributor-level or higher user accounts exist on the site

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

Until a patched version is released, disable or remove the plugin. If continued use is required, implement application-level restrictions on the shortcode or migrate to a secure alternative plugin.

Recommended fix Moderate confidence

Latest version of Inpersttion For Theme plugin (newer than 1.0)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Inpersttion For Theme' plugin (verify exact spelling in the plugins list)
  4. Check if an update is available for this plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  7. After updating, verify the new version number in the plugins list

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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