XenForo 2.3.0 Released Full | XenForo 2.3 ENXF

Released 2x XenForo 2.3.0 Released Full | XenForo 2.3 ENXF 2.3.8

No permission to download
XenForo 2.3.8 is now available for all Nulled customers to download. We strongly recommend that all customers running previous versions of XenForo 2.3 upgrade to this release to benefit from increased stability.

XenForo 2.3.8 also includes a number of smaller new features and improvements which you can read about here:

Some of the changes in XF 2.3.8 include:

The following public templates have had changes:
  • _help_page_privacy_policy
  • account_reactions
  • account_visitor_menu
  • attachment_macros
  • bb_code_tag_attach
  • core.less
  • core_action_bar.less
  • embed_resolver_thread
  • helper_attach_upload
  • lightbox.less
  • login_password_confirm
  • member_about
  • member_macros
  • member_recent_content
  • member_tooltip.less
  • message.less
  • message_macros
  • news_feed_attached_images
  • passkeys_macros
  • report_view
  • setup.less
  • share_page_macros
  • tag_macros
  • tag_search
  • two_step_totp
Where necessary, the merge system within the "outdated templates" page should be used to integrate these changes.

As always, new releases of XenForo are free to download for all customers with active licenses. You may now upgrade from your admin control panel or grab the new version from the customer area.

Current requirements​

Please note that XenForo 2.3 has higher system requirements than earlier versions.

The following are minimum requirements:
  • PHP 7.2 or newer (PHP 8.3 recommended)
  • MySQL 5.7 and newer (Also compatible with MariaDB/Percona etc.)
  • All of the official add-ons require XenForo 2.3.
  • Enhanced Search requires at least Elasticsearch 7.2.

Installation and upgrade instructions​

Full details of how to install and upgrade XenForo can be found in the XenForo 2 Manual. We strongly recommend upgrading directly from within your control panel.
  • Like
Reactions: paulike
reupload fix error api and hash file
Some of the changes in XF 2.3.7 include:

The following public templates have had changes:
  • PAGE_CONTAINER
  • account_banner
  • app_nav.less
  • conversation_message_macros
  • core_block.less
  • core_button.less
  • core_input.less
  • core_tab.less
  • editor_override.less
  • helper_js_global
  • member_view
  • passkeys_macros
  • post_macros
  • profile_post_macros
  • tag_macros
  • token_input
Where necessary, the merge system within the "outdated templates" page should be used to integrate these changes.

Security Fix​

Today we are advising all customers running XenForo that a potential security vulnerability has been identified. All affected customers running XenForo 2.3.0 should upgrade to XenForo 2.3.0 Release Candidate 1, including XenForo Media Gallery 2.3.0 Release Candidate 1 if needed.

If you also have active installs of XenForo 2.2 or XenForo 2.1 you should refer to the earlier thread with details and patch.

The issue relates to a potential cross-site request forgery and code injection vulnerability which could lead to a remote code execution (RCE) or cross-site scripting (XSS) exploit.

Shortly after the release of Release Candidate 1, we identified an issue related to editing node-like permissions. A very minor bug was surfaced by the changes today. Specifically one of our view class names was using a \ instead of a :

Due to a localised shortage of version numbers (we cannot increment the version to a patch release for release candidates) we have released Release Candidate 2 to address this.

The specific files with changes are:
  • src/XF/Admin/Controller/Node.php
  • src/XF/Admin/Controller/Permission.php
As we get ever closer to the fabled "release candidate" stage and the eventual stable release, today we are releasing the eighth beta for XenForo 2.3! Nothing particularly noteworthy this week other than a number of bug fixes.

We strongly recommend anyone testing 2.3 during this beta period upgrade as each beta version is released.
Welcome to 2.3.0 Beta 7! Since our last release we have been mostly focusing again on bug fixes and stability, though we do have an interesting change to note related to multibyte strings, specifically URL romanization. If available, we now use the intl extension and perform a multi-layered process for normalizing and transliterating strings. This is now much more intelligent as it handles some special cases for certain locales (based on the default language of the forum).

We also have a new option for controlling the output of emojis in URLs. You can leave them URL encoded, remove them, or convert them to a string based on the emoji name. This also requires the intl extension.
This week (and a bit) we have been extremely busy working towards that enticing milestone of a stable release. There's still a little while to go with a healthy number of bugs, feedback and other bits in our backlog that we'd like to work through, but each release represents a significant amount of effort and progress towards the end goal.

While we have mostly focused on bug fixes and other stability improvements, this has resulted in some notable changes which you should be aware of.
Top