Alle 5 veröffentlichten Versionen haben alle Prüfungen bestanden
Jede Version wird bereinigt, mit dem Lizenzcode des Anbieters verglichen und gescannt, bevor sie committet wird. Eine Version, die die Prüfung nicht besteht, wird nicht veröffentlicht. Letzter Scan .
Veröffentlichte Versionen5
Gescannte Dateien3K
Geprüfte Funde77
Zurückgehaltene Versionen0
Zurückgehalten: Archive dieses Plugins, die die automatischen Prüfungen nicht bestanden haben und nicht veröffentlicht werden. Geprüfte Funde: Treffer der Regeln, die vor der Veröffentlichung geprüft und geklärt wurden.
Web-Shells, verschleierte Loader, kodiertes PHP und bekannte Nulling-Muster (php-malware-finder plus MeteorGPL-Regeln).
PHP-AnalyseHeuristik v20
Analyse auf Token-Ebene: Remote-Includes, Request-Eingaben, die Shell-Funktionen erreichen, Decoder, die eval speisen, in Bildern, Schriften oder Archiven verstecktes PHP, Überschreibungen von Server-Handlern.
LizenzintegritätSignatursatz f3bba935e4a8
Lizenz-, Aktivierungs- und Update-Code wird mit dem eigenen Code des Anbieters und der vorherigen Version verglichen; veränderter Lizenzcode wird nie veröffentlicht.
PHP-SyntaxPHP 8.3.36
Jede PHP-Datei lässt sich mit der PHP-Version parsen, die das Repository unterstützt.
Grafiken, Schriften, Medien und Demo-Inhalte, die möglicherweise separat lizenziert sind, werden durch Platzhalter ersetzt oder entfernt (Lizenzprofil gpl-full).
Eine Sicherheitslücke melden. Sicherheitsprobleme im eigenen Code des Plugins sind Sache des Anbieters gVectors Team; melden Sie sie dort. Probleme mit einem Paket, wie es dieses Repository verbreitet – eine Datei, die nicht dort sein sollte, ein Scan, der etwas übersehen hat –, gehen an packages@meteorgpl.com und werden innerhalb von 48 Stunden beantwortet.
Was bei einem Fund geschieht. Die betroffenen Versionen werden aus dem Repository zurückgezogen, die Beobachter des Pakets werden benachrichtigt, und eine korrigierte Version wird veröffentlicht, sobald eine alle Prüfungen besteht.
Rechteinhaber. Die Takedown-Richtlinie beschreibt, wie ein Paket entfernt wird.
Bekannte Schwachstellen
Öffentliche Schwachstellenmeldungen zu wpForo, die betroffenen Versionen und die Version in diesem Repository, die sie behebt. Beobachter des Pakets und Konten, die bekanntermaßen eine betroffene Version einsetzen, werden benachrichtigt.
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'telegram' profile field in versions up to, and including, 3.1.6. This is due to insufficient input sanitization and output escaping in the profile_update action — the raw $_POST['data'] array is copied into a $custom_fields variable before validate() and sanitize() run, both of which operate only on a parallel $user reference, leaving $custom_fields unsanitized when it is persisted via update_custom_fields(); on render, wpforo_decode() reverses the entity encoding and the value is echoed without escaping in field_wrap_profile(). This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Abhilfe: Update to version 3.1.7, or a newer patched version
CWE-79: Improper Neutralization of Input During Web Page Generation
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 3.1.5. This is due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Abhilfe: Update to version 3.1.6, or a newer patched version
CWE-79: Improper Neutralization of Input During Web Page Generation
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.1.5. This is due to deserialization of untrusted input. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
Abhilfe: Update to version 3.1.6, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to Denial of Service in versions 3.0.0 through 3.1.5. This is due to trust in attacker-controlled HTTP headers (HTTP_CF_CONNECTING_IP, HTTP_X_FORWARDED_FOR) over REMOTE_ADDR for IP-based rate limiting in the get_client_ip() function. This makes it possible for unauthenticated attackers to exhaust the site owner's metered AI credits by repeatedly spoofing the IP address header used to key per-visitor rate limits, bypassing the restriction entirely.
Abhilfe: Update to version 3.1.6, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.1.5. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to take over another guest author's forum post and modify its title, body, author name, and stored owner email address. This requires that guest posting and editing are enabled on the forum, and that the attacker knows the target guest author's email address.
Abhilfe: Update to version 3.1.6, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to SQL Injection via the 'referer' parameter in all versions up to, and including, 2.4.17. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Abhilfe: Update to version 3.0.0, or a newer patched version
CWE-89: Improper Neutralization of Special Elements used in an SQL Command
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 3.1.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to manipulate account reputation statuses.
Abhilfe: Update to version 3.1.3, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 3.1.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Abhilfe: Update to version 3.1.2, or a newer patched version
CWE-79: Improper Neutralization of Input During Web Page Generation
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.1.1 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete other user's chat messages.
Abhilfe: Update to version 3.1.2, or a newer patched version
CWE-639: Authorization Bypass Through User-Controlled Key
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'location' Profile Field in all versions up to, and including, 3.1.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The sanitize_text_field() function applied at input does not encode double quotes, allowing attribute breakout via a payload that escapes the href attribute context and injects event handler attributes.
Abhilfe: Update to version 3.1.2, or a newer patched version
CWE-79: Improper Neutralization of Input During Web Page Generation
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 3.0.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Abhilfe: Update to version 3.1.0, or a newer patched version
CWE-89: Improper Neutralization of Special Elements used in an SQL Command
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 3.1.0. This makes it possible for unauthenticated attackers to perform an unauthorized action.
Abhilfe: Update to version 3.1.1, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 3.1.0 via deserialization of untrusted input. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
Abhilfe: Update to version 3.1.1, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions up to, and including, 3.0.6. This makes it possible for unauthenticated attackers to perform an unauthorized action.
Abhilfe: Update to version 3.0.7, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 3.0.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Abhilfe: Update to version 3.0.5, or a newer patched version
CWE-89: Improper Neutralization of Special Elements used in an SQL Command
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions up to 3.0.2. This makes it possible for unauthenticated attackers to perform an unauthorized action.
Abhilfe: Update to version 3.0.2, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to and including 3.0.5. This is due to two compounding flaws: the Members::update() method does not validate or restrict the value of file-type custom profile fields, allowing authenticated users to store an arbitrary path instead of a legitimate upload path; and the wpforo_fix_upload_dir() sanitization function in ucf_file_delete() only remaps paths that match the expected pattern, and it is passed directly to the unlink() function. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Note: The vulnerability requires a file custom field, which requires the wpForo - User Custom Fields addon plugin.
Abhilfe: Update to version 3.0.6, or a newer patched version
CWE-22: Improper Limitation of a Pathname to a Restricted Directory
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to unauthorized modification of data due to the use of `extract($args, EXTR_OVERWRITE)` on user-controlled input in the `edit()` method of `classes/Posts.php` in all versions up to, and including, 2.4.16. The `post_edit` action handler in `Actions.php` passes `$_REQUEST['post']` directly to `Posts::edit()`, which calls `extract($args, EXTR_OVERWRITE)`. An attacker can inject `post[guestposting]=1` to overwrite the local `$guestposting` variable, causing the entire permission check block to be skipped. The nonce check uses a hardcoded `wpforo_verify_form` action shared across all 8 forum templates, so any user who can view any forum page obtains a valid nonce. This makes it possible for authenticated attackers, with Subscriber-level access and above, to edit the title, body, name, and email fields of any forum post, including posts in private forums, admin posts, and moderator posts. Content passes through `wpforo_kses()` which strips JavaScript but allows rich HTML.
Abhilfe: Update to version 3.0.0, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to and including 3.0.2. This is due to a two-step logic flaw: the topic_add() and topic_edit() action handlers accept arbitrary user-supplied data[*] arrays from $_REQUEST and store them as postmeta without restricting which fields may contain array values. Because 'body' is included in the allowed topic fields list, an attacker can supply data[body][fileurl] with an arbitrary file path (e.g., wp-config.php or an absolute server path). This poisoned fileurl is persisted to the plugin's custom postmeta database table. Subsequently, when the attacker submits wpftcf_delete[]=body on a topic_edit request, the add_file() method retrieves the stored postmeta record, extracts the attacker-controlled fileurl, passes it through wpforo_fix_upload_dir() which only rewrites legitimate wpforo upload paths and returns all other paths unchanged, and then calls wp_delete_file() on the unvalidated path. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files writable by the PHP process on the server, including critical files such as wp-config.
Abhilfe: Update to version 3.0.3, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 2.4.16. This is due to a missing file name/path validation against path traversal sequences. This makes it possible for authenticated attackers, with subscriber level access and above, to delete arbitrary files on the server by embedding a crafted path traversal string in a forum post body and then deleting the post.
Abhilfe: Update to version 2.4.17, or a newer patched version
CWE-22: Improper Limitation of a Pathname to a Restricted Directory
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to time-based SQL Injection via the 'wpfob' parameter in all versions up to, and including, 2.4.14 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Abhilfe: Update to version 2.4.15, or a newer patched version
CWE-89: Improper Neutralization of Special Elements used in an SQL Command
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.4.13 via deserialization of untrusted input in the 'wpforo_display_array_data' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.
Abhilfe: Update to version 2.4.14, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to generic SQL Injection via the `post_args` and `topic_args` parameters in all versions up to, and including, 2.4.12 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Abhilfe: Update to version 2.4.13, or a newer patched version
CWE-89: Improper Neutralization of Special Elements used in an SQL Command
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 2.4.10. This makes it possible for unauthenticated attackers to perform an unauthorized action.
Abhilfe: Update to version 2.4.11, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to SQL Injection via the Subscriptions Manager in all versions up to, and including, 2.4.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Abhilfe: Update to version 2.4.10, or a newer patched version
CWE-89: Improper Neutralization of Special Elements used in an SQL Command
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to error‐based or time-based SQL Injection via the get_members() function in all versions up to, and including, 2.4.8 due to missing integer validation on the 'offset' and 'row_count' parameters. The function blindly interpolates 'row_count' into a 'LIMIT offset,row_count' clause using esc_sql() rather than enforcing numeric values. MySQL 5.x’s grammar allows a 'PROCEDURE ANALYSE' clause immediately after a LIMIT clause. Unauthenticated attackers controlling 'row_count' can append a stored‐procedure call, enabling error‐based or time‐based blind SQL injection that can be used to extract sensitive information from the database.
Abhilfe: Update to version 2.4.9, or a newer patched version
CWE-89: Improper Neutralization of Special Elements used in an SQL Command
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.4.6 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform unauthorized actions.
Abhilfe: Update to version 2.4.7, or a newer patched version
CWE-639: Authorization Bypass Through User-Controlled Key
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 2.4.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.
Abhilfe: Update to version 2.4.6, or a newer patched version
CWE-79: Improper Neutralization of Input During Web Page Generation
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.4.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges.
Abhilfe: Update to version 2.4.4, or a newer patched version
Korrigierte Version im Repository verfügbar: 3.2.1
composer require meteorgpl-plugin/wpforo:^3.2.1
3 Versionen in diesem Repository sind betroffen: 2.4.1, 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to arbitrary file read due to insufficient input validation in the 'update' method of the 'Members' class in all versions up to, and including, 2.4.1. This makes it possible for authenticated attackers, with subscriber-level privileges or higher, to read arbitrary files on the server.
Abhilfe: Update to version 2.4.2, or a newer patched version
Korrigierte Version im Repository verfügbar: 2.4.1
composer require meteorgpl-plugin/wpforo:^2.4.1
2 Versionen in diesem Repository sind betroffen: 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.3.4. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.
Abhilfe: Update to version 2.3.5, or a newer patched version
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Korrigierte Version im Repository verfügbar: 2.4.1
composer require meteorgpl-plugin/wpforo:^2.4.1
2 Versionen in diesem Repository sind betroffen: 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.3.4 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform an unauthorized action.
Abhilfe: Update to version 2.3.5, or a newer patched version
CWE-639: Authorization Bypass Through User-Controlled Key
Korrigierte Version im Repository verfügbar: 2.4.1
composer require meteorgpl-plugin/wpforo:^2.4.1
2 Versionen in diesem Repository sind betroffen: 2.3.1, 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to SQL Injection via the 'slug' attribute of the 'wpforo' shortcode in all versions up to, and including, 2.3.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Abhilfe: Update to version 2.3.4, or a newer patched version
CWE-89: Improper Neutralization of Special Elements used in an SQL Command
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 2.2.3. This is due to incorrect assignment of user permissions during registration. This makes it possible for unauthenticated attackers to elevate their privileges to that of an administrator.
Abhilfe: Update to version 2.2.4, or a newer patched version
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.2.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Abhilfe: Update to version 2.2.4, or a newer patched version
CWE-79: Improper Neutralization of Input During Web Page Generation
Korrigierte Version im Repository verfügbar: 2.3.1
composer require meteorgpl-plugin/wpforo:^2.3.1
1 Version in diesem Repository ist betroffen: 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.2.8. This is due to missing or incorrect nonce validation on the logout() function. This makes it possible for unauthenticated attackers to log out other users via a forged request granted they can trick a site's user into performing an action such as clicking on a link.
Abhilfe: Update to version 2.2.9, or a newer patched version
Korrigierte Version im Repository verfügbar: 2.3.1
composer require meteorgpl-plugin/wpforo:^2.3.1
1 Version in diesem Repository ist betroffen: 2.2.4
Details
The wpForo Forum plugin for WordPress is vulnerable to unauthorized control of data due to a missing capability check on an unknown function in all versions up to, and including, 2.2.5. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.
Abhilfe: Update to version 2.2.6, or a newer patched version
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘wpforo_debug’ function in versions up to, and including, 2.1.8 due to insufficient input sanitization and output escaping. 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.
Abhilfe: Update to version 2.1.9, or a newer patched version
CWE-79: Improper Neutralization of Input During Web Page Generation
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to Local File Include, Server-Side Request Forgery, and PHAR Deserialization in versions up to, and including, 2.1.7. This is due to the insecure use of file_get_contents without appropriate verification of the data being supplied to the function. This makes it possible for authenticated attackers, with minimal permissions such as a subscriber, to retrieve the contents of files like wp-config.php hosted on the system, perform a deserialization attack and possibly achieve remote code execution, and make requests to internal services.
Abhilfe: Update to version 2.1.8, or a newer patched version
CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to HTML Injection in versions up to, and including, 2.0.9. This is due to insufficient escaping and sanitization of user supplied input. This makes it possible for authenticated attackers, with subscriber-level permissions and above to inject HTML content on pages.
Abhilfe: Update to version 2.1.0, or a newer patched version
CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 2.0.5. This makes it possible for authenticated attackers, with subscriber-level access or higher, to mark any forum post as private/public.
Abhilfe: Update to version 2.0.6, or a newer patched version
CWE-639: Authorization Bypass Through User-Controlled Key
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to arbitrary file uploads due to missing protections or file validations in versions up to, and including, 2.0.9. This makes it possible for authenticated attackers, with minimal permissions, to upload arbitrary files on the affected sites server which may make remote code execution possible.
Abhilfe: Update to version 2.1.0, or a newer patched version
CWE-434: Unrestricted Upload of File with Dangerous Type
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.0.9. This is due to missing or incorrect nonce validation on the profile_cover_delete function. This makes it possible for unauthenticated attackers to delete forum users, via forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Abhilfe: Update to version 2.1.0, or a newer patched version
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 2.0.5. This makes it possible for authenticated attackers, with subscriber-level access or higher, to mark any forum post as solved/unsolved.
Abhilfe: Update to version 2.0.6, or a newer patched version
CWE-639: Authorization Bypass Through User-Controlled Key
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.0.5. This is due to missing or incorrect nonce validation on one of its functions. This makes it possible for unauthenticated attackers to execute that function, via forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Abhilfe: Update to version 2.0.6, or a newer patched version
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.0.5. This is due to missing or incorrect nonce validation on various AJAX actions. This makes it possible for unauthenticated attackers to invoke the associated functions (leading to post deletion for example), via forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Abhilfe: Update to version 2.0.6, or a newer patched version
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum WordPress plugin before 1.9.7 did not validate the redirect_to parameter in the login form of the forum, leading to an open redirect issue after a successful login. Such issue could allow an attacker to induce a user to use a login URL redirecting to a website under their control and being a replica of the legitimate one, asking them to re-enter their credentials (which will then in the attacker hands)
Abhilfe: Update to version 1.9.7, or a newer patched version
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
An issue was discovered in the update function in the wpForo Forum plugin before 1.5.2 for WordPress. A registered forum user is able to escalate privilege to the forum administrator without any form of user interaction.
Abhilfe: Update to version 1.5.2, or a newer patched version
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
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.
Abhilfe: Update to version 1.4.12, or a newer patched version
CWE-79: Improper Neutralization of Input During Web Page Generation
Korrigierte Version im Repository verfügbar: 2.2.4
composer require meteorgpl-plugin/wpforo:^2.2.4
Keine Version in diesem Repository ist betroffen.
Details
The wpForo Forum plugin for WordPress is vulnerable to Blind SQL Injection via the ‘wpfo’ parameter in versions up to, and including, 1.4.12 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Abhilfe: Update to version 1.4.13, or a newer patched version
CWE-89: Improper Neutralization of Special Elements used in an SQL Command
Schwachstellendaten: Wordfence Intelligence. Jede Sicherheitsmeldung verweist auf ihren Eintrag dort.
Copyright 2012-2026 Defiant Inc.. Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy. https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/
Copyright 1999-2026 The MITRE Corporation. CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy. https://www.cve.org/Legal/TermsOfUse