Premium 1.16.1 / Free 3.6.1

relevanssi_index_custom_fields relevanssi_post_to_index relevanssi_tax_term_additional_content

I was told today that there is a security vulnerability in Relevanssi. It is possible to set the post type and taxonomy weights to values that are not numeric, and those values will be inserted into SQL queries, making SQL injection possible.

However, it requires either admin access to the WordPress dashboard or direct access to the server to set the values, and despite trying different approaches, the worst I could do was to break the Relevanssi search (I tried to destroy tables from the database, but couldn’t make that happen). So, as far as I can tell, this is a relatively minor security vulnerability.

However, all security vulnerabilities are taken seriously and fixed immediately. Version 1.16.1 of Relevanssi Premium and 3.6.1 of the free Relevanssi are safe from this vulnerability.

There are also other improvements in these versions:

Premium: Multisite meta queries didn’t work properly.
Premium: The filter relevanssi_tax_term_additional_content now works even when the taxonomy description is empty.
Premium: Relevanssi taxonomy term indexing is moved to a later priority (from 10 to 9999) to make sure all term data is available for indexing.
Both: Search and Filter shortcode is added to the blacklist.
Both: Groups plugin is now supported automatically to restrict access to posts.
Both: The filter relevanssi_index_custom_fields now works even if the custom field setting is empty.
Both: The filter relevanssi_post_to_index now has a second parameter. For posts, it simply repeats the post object, but for taxonomy terms, it has the term object.

The free version is available from the plugin repository. Premium is available through WordPress plugin updates or from the download page.

Your account

Not logged in. Log in to see your license details.

Search

Popular Resources

Relevanssi and languages

…extra umlauts thrown in). This alphabet use restricts the Premium “Did you mean” feature to text in the Latin alphabet. The simpler “Did you mean” feature in the free version of Relevanssi should work with most character sets, as it uses the user searches, but it’s less reliable in other……’rlv_use_jieba’ ); function rlv_use_jieba( $string ) { $string = jieba( $string, 1, 1500 ); $string = @implode( ‘ ‘, $string ); return $string; } For Japanese, there’s Limelight. Did you mean suggestions: limited to Latin characters While Relevanssi can search Arabic, Russian or other non-Latin character sets, the “Did you……mean” suggestions in Relevanssi Premium only support Latin characters. The way these suggestions work is that when Relevanssi searches, Relevanssi then modifies the search term in different ways by adding or removing letters in it. Relevanssi does these modifications with the Latin alphabet (mainly the English alphabet, with a few…

WooCommerce: Indexing product variation SKUs for main product

Relevanssi can index product and product variation SKUs for WooCommerce products: just add _sku to list of custom fields to…

Adjusting search throttle

…$limit ) { return 250; } ); If necessary, you can adjust the value (250) to a lower number. Anything over 100 should be safe. Throttle and termless searches The throttle is always on when there’s no search term involved in the search. Otherwise, the search would return all posts……always on when there’s no search term involved in the search. Otherwise, the search would return all posts on the site as a result. That’s too much. If you, for some reason, want to disable the throttle completely in all cases, you can use this line: remove_filter( ‘relevanssi_query_filter’, ‘relevanssi_limit_filter’ );…If Relevanssi Premium causes out-of-memory problems, make sure you have the “Throttle searches” option checked. However, if that doesn’t work and you’re still getting out of memory issues, you can try making the throttle tighter. The limit can be adjusted by adding this line to your site: add_filter( ‘pre_option_relevanssi_throttle_limit’, function(…