BP Profile Shortcodes Extra plugin Review
BP Profile Shortcodes Extra was closed on WordPress.org in November 2024 for a security issue. Checked 15 Nov 2026: CVEs, BuddyPress 14 and alternatives.

BP Profile Shortcodes Extra is closed on WordPress.org and should not be installed. The plugin directory closed it on 19 November 2024 with the reason “Security Issue”, the last release was 2.6.0, and three published advisories cover versions up to 2.6.0, one of them a SQL injection. We checked all of this on 15 November 2026. This post keeps the review, because people still search for it, and then shows what to use instead.
If you already run it, the shortcodes keep rendering today, but no one is patching them. The safest move is to list which shortcodes your pages use, replace them with BuddyPress blocks or a small shortcode of your own (code below), and then delete the plugin. If you want the short version of the replacement, jump to “What should I use instead?”.
Is BP Profile Shortcodes Extra still maintained?
No. Here is what the plugin directory and its own files say, checked on 15 November 2026.
Item | What we found |
|---|---|
Status on WordPress.org | Closed on 19 November 2024. Reason given: Security Issue. Not available for download. |
Last release | 2.6.0. The changelog entry adds follower and following lists to |
Last code change in the repository | 23 July 2024, by the author, Venutius. |
Tested up to (readme) | WordPress 6.6. Current WordPress is 7.1.x. |
BuddyPress 12 and 14 compatibility | Never declared. See the section below. |
Ratings, installs, support-resolved share | Not shown by the WordPress.org API for a closed plugin, so we cannot quote them. |
You can still read the source in the public repository, which is how we checked the shortcode list in this post. Reading it is not the same as being safe to run it.
Is it safe to keep using?
We would not run it on a public site. Three advisories exist for this plugin, and the plugin was closed without a fixed version following them. We cite the CVE records, which name the reporting sources.
ID | Type | Affected versions | Published | Reported by |
|---|---|---|---|---|
Cross-site scripting (XSS) | 2.5.2 and below | 22 November 2023 | Patchstack | |
Time-based SQL injection through the | Up to and including 2.6.0 | 3 December 2024 | Wordfence | |
Stored XSS | Up to and including 2.6.0 | 9 January 2025 | Patchstack |
Both 2.6.0 entries need a logged-in account at Contributor level or higher, according to the records. That lowers the risk on a site where only staff can log in. It does not help on a community site where members register, because members are exactly the accounts these entries describe.
The SQL injection is visible in the source. In bpps_profile_field, the default method builds its query by pasting the shortcode’s tab value straight into the SQL string, without $wpdb->prepare(). The Wordfence record points at that same file and line. A plugin that keeps working today and gets no future patch is the worst combination for a tool that runs on user-editable pages.
We did not find an advisory that says a fixed version exists. If you see a fork claiming to fix it, treat it as unreviewed code and read it before you trust it.
Does it work with BuddyPress 12 and 14?
It might render on your site, but it was not built for the current BuddyPress. We read the 2.6.0 source against BuddyPress 14.5.4, released on 23 October 2026.
- BuddyPress 12.0 moved member and group URLs to
bp_members_get_user_url()and deprecatedbp_core_get_user_domain(). The plugin’s own code does not call the deprecated function, and it does referencebp_members_get_user_url, so links are likely fine. - The default
bpps_profile_fieldpath reads the xProfile tables directly instead of calling BuddyPress functions. A schema change in a later BuddyPress release would break it silently. - The readme was last tested against WordPress 6.6, and BuddyPress 14.5.4 requires WordPress 6.1 or newer, so there is no test on current versions either way.
So the honest answer is “unknown and unsupported”. Because the plugin is closed, no one will fix it if it breaks. Our guide to using BuddyPress in WordPress covers the BuddyPress 12 and 14 URL changes, which matter for any plugin that builds profile links.
What did BP Profile Shortcodes Extra actually do?
It gave site owners shortcodes to print pieces of a member profile or a group anywhere on a page or post. The author, Venutius, built it as a fork of the older BP Profile Shortcodes plugin and added profile headers, cover images and member lists. Its goal, in the readme, was to let you build member and group dashboards out of shortcodes. There was also a button in the Classic editor and a set of blocks.
Every shortcode below exists in the 2.6.0 source. We listed them from add_shortcode() calls, 27 in total, rather than from the old review.
Member (profile) shortcodes
Shortcode | What it shows |
|---|---|
| Display name, as text or a link |
| Username, as text or a link |
| Email address |
| Avatar as an image, a bare URL, or a link to the profile |
| Cover image in the same three forms |
| Cover image, avatar and name together |
| One xProfile field, with |
| Link to the profile or to the edit screen |
| Link to message that member |
| Friends, groups, followers, following, or site-wide member and group lists |
| The activity “What’s New” post form |
Group shortcodes
Shortcode | What it shows |
|---|---|
| Group avatar in three forms |
| Group cover image in three forms |
| Cover image, avatar and group name |
| Group URL or a link with your text |
| Member names or avatars |
| Group description |
| Group custom field |
Most shortcodes defaulted to the member viewing the page when you did not pass a user. The readme examples include [bpps_profile_displayname user_id="1" class="member-name"] and [bpps_profile_field field="Details" user_id="bill" tab="More"]. The old version of this review listed an error_msg attribute for every shortcode, and we found it in only some of them, so do not count on it.
What should I use instead?
There is no single drop-in replacement, because nothing else ships a full set of per-field profile shortcodes for current BuddyPress. Pick by what you were showing.
You were showing | Use this now | Notes |
|---|---|---|
A member card or list on a page | BuddyPress “Member”, “Members”, “Dynamic Members List”, “Recently Active Members” or “Online Members” blocks | In BuddyPress 14.5.4 core. The Member block takes avatar size, mention slug, action button and cover image options. |
A group card or list | BuddyPress “Group”, “Groups” or “Dynamic Groups List” blocks | In core. The Group block has a description toggle, action button and cover image option. |
Recent activity on a page | “Latest Activities” and “Embed an activity” blocks | In core. |
One profile field in text | Your own small shortcode (snippet below) | About 30 lines. You control the escaping and the visibility check. |
Member, group and activity listings in a layout anywhere | Made by our team. It gives you | |
A searchable member directory | Search forms and a | |
A whole member profile and community layer | BuddyX or Reign with BuddyNext (see below) | A rebuild, not a patch. |
We checked the plugins above in the WordPress.org API on 15 November 2026. Shortcodes & Elementor Widgets For BuddyPress is version 3.0.1, updated 4 November 2026, tested to WordPress 7.1.4, with 500+ installs and a 92% rating over only 10 reviews. That is too few reviews to judge it by, and we say so because we are the authors.
How do I show a profile field without the plugin?
Write a short shortcode that calls xprofile_get_field_data(), the BuddyPress function for this. The snippet below prints one field for the viewed profile, a chosen member, or the logged-in member. It prints only fields set to the Public visibility level, because xprofile_get_field_data() does not check visibility on its own. We linted it with PHP 8 and confirmed each BuddyPress function it calls exists in BuddyPress 14.5.4. We did not run it on a live community. Test it on a staging site first.
<?php
/**
* Plugin Name: Member Field Shortcode
* Description: [member_field field="Location"] prints one public xProfile field.
*/
add_shortcode( 'member_field', function ( $atts ) {
if ( ! function_exists( 'xprofile_get_field_data' ) ) {
return '';
}
$atts = shortcode_atts(
array(
'field' => '',
'user_id' => 0,
),
$atts,
'member_field'
);
// Default to the profile being viewed, then to the logged-in member.
$user_id = absint( $atts['user_id'] );
if ( ! $user_id ) {
$user_id = bp_displayed_user_id() ? bp_displayed_user_id() : get_current_user_id();
}
$field_id = xprofile_get_field_id_from_name( sanitize_text_field( $atts['field'] ) );
if ( ! $user_id || ! $field_id ) {
return '';
}
// xprofile_get_field_data() ignores visibility, so only print public fields.
if ( 'public' !== xprofile_get_field_visibility_level( $field_id, $user_id ) ) {
return '';
}
return esc_html( (string) xprofile_get_field_data( $field_id, $user_id, 'comma' ) );
} );
Put it in a small must-use plugin or your child theme, not in a page. Then use [member_field field="Location"] on a profile template, or [member_field field="Location" user_id="12"] anywhere else. The field name is the label as you typed it in Users > Profile Fields. It reads through BuddyPress, so a future table change will not break it, which is the weakness of the old default path. Checked on 15 November 2026.
If you need the field in a template instead of a post, our guide to custom BuddyPress profile fields covers the xProfile API in more depth, and the BuddyPress hooks cheat sheet lists the hooks to print extra markup in member loops.
What can I do today if I cannot remove it yet?
Some sites cannot swap a shortcode on forty pages in an afternoon. These steps cut the exposure while you plan the move. They reduce the risk, they do not remove it.
- Check who holds a Contributor, Author, Editor or Administrator role. The 2.6.0 advisories need Contributor level or above, so a clean user list matters. In Users, filter by role and remove accounts you do not recognise.
- Make sure new registrations default to Subscriber. In Settings > General, the “New User Default Role” setting controls it.
- Stop using the shortcodes that take a free-text attribute from content editors where you can. The SQL injection is in the
tabvalue ofbpps_profile_field, so pages that never use that shortcode are not exposing that path through content, although the plugin file is still loaded. - Put the replacement on a staging copy now, and set a date to deactivate the plugin on the live site. A date matters, because “later” is how closed plugins stay installed for years.
Do not rely on a firewall rule you wrote yourself as the only protection. If your host or security plugin offers virtual patching for this plugin, ask them which CVE IDs it covers, using the three above.
How do the old shortcodes map to BuddyPress blocks?
This is the practical translation for the most common uses. The block names come from the block files in BuddyPress 14.5.4.
Old shortcode | Closest current option | What you lose |
|---|---|---|
| Member block ( | The block shows one member with avatar, name and an optional cover image. You pick the member in the editor, so it is not “whoever is viewing”. |
| Members, Dynamic Members, Recently Active Members or Online Members blocks | No friends-of-this-user or following lists. Those need your own query. |
| Group block ( | You choose the group in the editor and toggle the description and cover image. |
| No single block for one group’s member list | Use a template, or the member and group blocks on the group page. |
| Your own | Nothing, if you keep the same link text. |
| The activity post form on the BuddyPress activity page | A standalone form on any page. |
| Your own | The |
BuddyPress 12.0 changed how profile URLs are built. If you write your own link shortcode, call bp_members_get_user_url() and not the deprecated bp_core_get_user_domain(). This one prints a link to any member’s profile. We linted it and confirmed both BuddyPress functions exist in 14.5.4. Test it before use.
<?php
// [member_link text="View profile"] links to a member's profile on BuddyPress 12 and later.
add_shortcode( 'member_link', function ( $atts ) {
if ( ! function_exists( 'bp_members_get_user_url' ) ) {
return '';
}
$atts = shortcode_atts( array( 'user_id' => 0, 'text' => '' ), $atts, 'member_link' );
$user_id = absint( $atts['user_id'] ) ? absint( $atts['user_id'] ) : get_current_user_id();
if ( ! $user_id ) {
return '';
}
$text = '' !== $atts['text'] ? $atts['text'] : bp_core_get_user_displayname( $user_id );
return sprintf( '<a href="%s">%s</a>', esc_url( bp_members_get_user_url( $user_id ) ), esc_html( $text ) );
} );
How do I move off the plugin without breaking pages?
- Back up the database. Then search your content for
[bpps_to find every page that uses a shortcode. In WP-CLI that iswp post list --post_type=any --s="[bpps_" --fields=ID,post_title, and a search of the Posts screen works too. Page builders and widgets store shortcodes in their own places, so check widgets and templates by hand. - List which shortcodes appear and map each to the table above. Display name, avatar and profile links usually become the Member block or your template.
- Replace on a staging copy first, one page at a time, and view each page as a logged-out visitor and as a member.
- Deactivate the plugin, reload every page you changed, and look for raw shortcode text in the output.
- Delete the plugin files. A deactivated plugin still sits on disk, and a plugin you no longer use is one more thing to keep patched or to forget about.
Common mistakes people report
These come from the plugin’s WordPress.org support forum. We read the threads on 15 November 2026 and paraphrase them. The forum is no longer a place to get help, since the plugin is closed, so this is a record of what went wrong.
- Fatal error after update or activation. Several members reported a critical error, including one tied to a specific line of the shortcodes file in October 2024 (thread), which shows as not resolved. Another report on a BuddyBoss site was resolved after the author found the cause was an added security measure and could not reproduce it on a clean install (thread).
- Group member list errors. The group members shortcode threw an error for more than one user in 2024, and the author marked it fixed in a later release (thread).
- Raw HTML printed instead of a link. A link shortcode showed markup as text in June 2024 and was fixed afterward (thread).
- “The tab name is invalid” or “The field name is invalid”. People who tried to show an extended profile field with
fieldandtabhit these messages, and one reader saidoption="Two"printed nothing (thread, not resolved). Our source read explains the first two: the default path matches the tab against the exact field-group name. Check spelling and capitals. - Shortcodes in block widgets. A user could not get shortcodes to work in block widget areas, and the thread ends without a confirmed fix (thread).
Which should I pick for my situation?
Our suggestion, in plain terms:
- You show member or group cards on a few pages. Use the BuddyPress blocks. They ship with BuddyPress, so they follow its updates.
- You show one or two profile fields in text. Use the snippet above and keep it in your own code.
- You place activity, members and groups listings across landing pages or in Elementor. Our free Shortcodes & Elementor Widgets For BuddyPress plugin does that. Its cons: only three shortcodes, no per-field profile output, and few reviews yet.
- You built entire member dashboards from
bpps_shortcodes. A plugin swap will not be enough, and the dashboard needs rebuilding. Our team builds community sites on BuddyX or Reign with BuddyNext, and that suits a new build or a planned move off BuddyPress. The cons are a real migration of members, groups and activity, and more work than a plugin swap. - You are on BuddyBoss Platform. It is a fork of BuddyPress with its own profile layouts. Compare it in our BuddyPress vs BuddyBoss post before adding any BuddyPress shortcode plugin to it.
If you are still choosing a community stack, our roundup of WordPress community plugins compares the current options with checked dates.
Frequently asked questions
Is BP Profile Shortcodes Extra still on WordPress.org?
No. It was closed on 19 November 2024 for a security issue, and the plugin page says it is not available for download.
When was it last updated?
Version 2.6.0 is the last release, and the last change to the repository was on 23 July 2024.
Does BP Profile Shortcodes Extra work with BuddyPress 14?
It may render, but it was never tested on BuddyPress 12 or 14, and it is closed, so a break will not be fixed. We would not rely on it.
Which vulnerabilities does it have?
CVE-2023-47815 (XSS, 2.5.2 and below), CVE-2024-11732 (time-based SQL injection, up to 2.6.0) and CVE-2025-22817 (stored XSS, up to 2.6.0). The 2.6.0 entries need a Contributor-level account or higher.
What replaces the bpps_profile_field shortcode?
Use your own shortcode built on xprofile_get_field_data(), as shown above, or print the field in a template. BuddyPress core has no profile field shortcode.
Do BuddyPress blocks replace profile shortcodes?
For member and group cards, lists and activity, yes. For a single profile field in running text, not by themselves.
Can I keep the plugin if only staff can log in?
The risk is lower, because the 2.6.0 advisories need a Contributor account. It is still unpatched and unsupported, so plan the move.
Facts, versions and advisories on this page were checked on 15 November 2026 against WordPress.org, the plugin’s public source and the CVE records linked above.


