ForumwpWordPress extension · Ultimatemember
CVE-2024-10879
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 ForumWP – Forum & Discussion Board plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg & remove_query_arg without appropriate escaping on the URL in all versions up to, and including, 2.1.2. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
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 ForumWP WordPress plugin is vulnerable to reflected XSS due to unsafe use of add_query_arg() and remove_query_arg() functions without proper URL escaping. Unauthenticated attackers can inject malicious scripts into URLs that execute when users click crafted links.
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
ForumwpWordPress extension
< 2.1.3CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Verify ForumWP plugin is installedCheck if the ForumWP plugin directory exists in your WordPress installation at wp-content/plugins/forumwp/ (or the plugin may be bundled with ultimatemember)Affected if The plugin directory is present
-
Locate the ForumWP plugin fileNavigate to wp-content/plugins/ in your WordPress installation and search for forumwp-related folders. The plugin may be named 'forumwp' or integrated within 'ultimatemember'Affected if ForumWP plugin files are found
-
Determine installed ForumWP versionOpen the main plugin PHP file (usually forumwp.php or similar in the plugin folder) and locate the version string in the plugin header comment, or check the readme.txt file for the 'Stable tag' versionAffected if Version is less than 2.1.3 (e.g., 2.1.2, 2.1.1, 2.0.x, etc.)
-
Confirm vulnerability is reachableThis is a reflected XSS vulnerability in URL handling functions. The flaw exists in any installation of ForumWP below version 2.1.3 when the plugin processes query arguments via add_query_arg() or remove_query_arg() without escapingAffected if Plugin version is below 2.1.3 and the plugin is active
You are affected if ForumWP (by Ultimatemember) is installed and active with a version lower than 2.1.3.
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.
dbcve · scoped2.1.3
Update ForumWP plugin to version 2.1.3 or later which contains the patch for proper URL escaping.
2.1.3
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the ForumWP plugin in the list
- Click the 'Update now' link if an update is available, or click 'Delete' and then reinstall version 2.1.3
- Alternatively, navigate to Dashboard > Updates and select ForumWP to update
- Verify the plugin is now running version 2.1.3
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Forumwp
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10879 — 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-2024-10879 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