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

CVE-2025-53328

HIGH · 7.5 CVSS v3.1 Published 2025-08-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Opinion Stage Poll, Survey & Quiz Maker Plugin by Opinion Stage social-polls-by-opinionstage allows PHP Local File Inclusion.This issue affects Poll, Survey & Quiz Maker Plugin by Opinion Stage: from n/a through <= 19.11.0.

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 · moderate confidence

The Opinion Stage Poll, Survey & Quiz Maker WordPress plugin (versions up to 19.11.0) contains a PHP Local File Inclusion (LFI) vulnerability (CWE-98) due to improper control of filename parameters in include/require statements. Attackers can exploit this to include arbitrary PHP files from the server, potentially achieving remote code execution.

MitigationUpdate the plugin to the latest patched version. If no patched version is available, manually audit the plugin code for vulnerable include/require statements and implement strict input validation on file path parameters to prevent directory traversal or arbitrary file inclusion.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 Opinion Stage plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Opinion Stage Poll, Survey & Quiz Maker', or check the /wp-content/plugins/ directory for a folder containing 'opinion-stage' in the name
    Affected if The plugin is found installed on the WordPress site
  2. Identify the installed plugin version
    In WordPress admin Plugins list, click on the plugin to view details and note the version number, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if The version is 19.11.0 or any earlier version (the vulnerability affects versions up to 19.11.0)
  3. Locate include/require statements in plugin files
    Search the plugin directory (/wp-content/plugins/opinion-stage/) for PHP files containing include, require, include_once, or require_once statements that use variables or request parameters for file paths, e.g., 'include($file)' or 'require($_GET["path"])'
    Affected if Such include/require patterns exist without proper input sanitization on file path parameters
  4. Check for accessible endpoints triggering the vulnerable include
    Identify PHP files in the plugin that process file path parameters from HTTP requests (GET/POST) and pass them to include/require statements without validation; test accessing those endpoints with a benign file path parameter
    Affected if The plugin processes file path parameters from requests and includes files based on user input without validation
  5. Verify directory traversal is possible
    Attempt to include a known file outside the plugin directory using a path like ../../../../../../etc/passwd in the vulnerable parameter (on a test/staging environment only); observe if the file content is returned or if PHP execution occurs
    Affected if The include/require allows directory traversal (../ sequences) to access arbitrary files on the server

A user is affected if the Opinion Stage plugin version is 19.11.0 or earlier and the plugin contains vulnerable include/require statements that process unvalidated file path parameters from HTTP requests.

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 plugin to the latest patched version. If no patched version is available, manually audit the plugin code for vulnerable include/require statements and implement strict input validation on file path parameters to prevent directory traversal or arbitrary file inclusion.

Recommended fix Moderate confidence

latest available version (newer than 19.11.0)

  1. 1. Update Opinion Stage Poll, Survey & Quiz Maker Plugin to the latest available version
  2. 2. After updating, verify the plugin functions correctly on your site
  3. 3. Review any security-related changelog or release notes for the new version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53328 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