dbcve.org
Wpforo ForumWordPress extension · Gvectors

CVE-2018-11709

MEDIUM · 6.1 CVSS v3.0 Published 2018-06-04
Fix available
A fix is available. Upgrade to 1.4.12 or later.
See remediation →
68/100
Remediation priority · Elevated
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
wpforo_get_request_uri in wpf-includes/functions.php in the wpForo Forum plugin before 1.4.12 for WordPress allows Unauthenticated Reflected Cross-Site Scripting (XSS) via the URI.

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 wpforo_get_request_uri function in the wpForo Forum plugin before version 1.4.12 fails to properly sanitize user-supplied input from the request URI before reflecting it in the HTTP response, allowing unauthenticated attackers to inject arbitrary JavaScript that executes in victims' browsers.

MitigationUpgrade the wpForo Forum plugin to version 1.4.12 or later to resolve the unsanitized URI reflection.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wpforo ForumWordPress extension
Affected:< 1.4.12

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Locate the wpForo Forum plugin installation
    Access your WordPress site via FTP or file manager and navigate to /wp-content/plugins/ folder. Look for a folder named 'wpforo' or 'wpforo-forum'. Inside, open the main plugin file (usually wpforo.php) and find the 'Version:' header in the plugin comments.
    Affected if The wpForo plugin folder exists and contains the plugin files.
  2. Determine the installed wpForo version
    Read the version number from the plugin file header (e.g., 'Version: 1.4.11') or from the readme.txt file in the plugin directory.
    Affected if The version shown is less than 1.4.12 (for example, 1.4.11, 1.4.10, 1.4.9, etc.).
  3. Verify the plugin is active
    Log into the WordPress admin dashboard, go to Plugins > Installed Plugins, and check whether wpForo Forum is listed as 'Active'.
    Affected if The plugin is currently active on the WordPress site.
  4. Confirm the vulnerable function exists
    Open the wpForo plugin main file and search for the string 'wpforo_get_request_uri' to confirm this function is present in the installed version.
    Affected if The function wpforo_get_request_uri is found in the plugin code.

You are affected if the wpForo Forum plugin is installed, active, and its version is lower than 1.4.12, allowing the unsanitized URI reflection to occur.

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.

From vendor data
Upgrade available Upgrade to 1.4.12 or later
Fixed in 1.4.12
Interim mitigation

Upgrade the wpForo Forum plugin to version 1.4.12 or later to resolve the unsanitized URI reflection.

Fix this in Wpforo Forum Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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