VaultWiki

VaultWiki [Paid] 4.1.10 Patch Level 1

No permission to buy ($15.00)
Overview Updates (7) History Discussion
As the default style on XenForo has responsive design, when using VaultWiki with XenForo, its content pages will also have responsive design. If you have a particular issue with a custom style, you may need to update VaultWiki's templates in accordance with your custom style.
 
pegasus said:
As the default style on XenForo has responsive design, when using VaultWiki with XenForo, its content pages will also have responsive design. If you have a particular issue with a custom style, you may need to update VaultWiki's templates in accordance with your custom style.
Click to expand...
Thanks, it means the latest XenForo and the latest VaultWiki combined will have a responsive design.
 
Digital Doctor said:
Can you insert Vaultwiki data into:
(1) posts (2) RM ?

What I mean is could I embed a vaultwiki entry right here where I am typing ?

[wiki]wiki.item[/wiki]
Click to expand...
This BB-Code will create a hyperlink to the wiki page called "wiki.item".

To embed a VaultWiki entry, you may want to use XenForo's EMBED BB-Code, same as for forum posts and other content, which embeds a preview of content wrapped with the premade widget block you're used to. As with other forum types, you need the canonical URL of the wiki content to create an EMBED. Requires XenForo 2.3+

If "wiki.item" is a wiki page, you can also use the VaultWiki INJECT BB-Code, which will embed the entire content of a VaultWiki page as a more inline presentation (without a styled wrapper). I don't use it often, but I think INJECT only works on wiki pages, not wiki entries.
Code: 
[INJECT]wiki.item[/INJECT]
 
Thanks. We had a failed Linux update. Hard to tell the exact reason the OS failed to boot, but it seemed likely due to overreliance on symlinks for system configuration files (which became outdated or disconnected). Unfortunately we had to rebuild the server from scratch, and apparently our notes from last time were a bit ... outdated. I don't think we lost any forum data / posts, since that's all stored elsewhere. As far as I can tell, most public-facing services are back online as of this evening.
 
In the wake of the recent server downtime, "we have extended licenses by an additional 7 days from the date of extension, for anyone with a timed license that was active during the affected period, even if that license expired between the downtime and the extension. That means that for any license that was active on November 8, 2025, the earliest day it will now expire is November 28, 2025, even if the license had already expired before today."
 
Changelog is here: https://www.vaultwiki.org/pages/Book/Documentation/VW4:Changelog-for-4-1-10
I will add a link within the release article.

The changelog should also be available as a button from the wiki version notification in your AdminCP, which is actually better as it filters changes based on the version you already have installed (some changelog issues may be older or newer than your version, or for a different version of XenForo).
 
smallwheels said:
When trying to access my profile on vaultwiki I end up with this:
Click to expand...
I will look into that problem. In the future if you have issues using a part of the support web site, a better place is to post/contact the support web site directly (if possible) or to message a support person (like me) directly.

Please try to limit this thread to general discussions of the VaultWiki add-on itself, general howto, can I?, etc. For issues in your environment, you can post here but still prioritize posting on the support web site, since it can better organize issues using 1 thread per question.

Unfortunately, here everything is limited to running together/being confused as one gigantic thread and your inquiry can easily get lost.
 
pegasus updated VaultWiki with a new update entry:

Changes in 4.1.8

(released September 23, 2024)
  • XenForo 2.3 Support
  • PHP 8.3 Support
  • Added public Entities for third-party add-on use
  • Reduced logging for deadlock errors
  • Over 180 other bug fixes and tweaks

WARNING! Because XenForo 2.3 includes significant changes to its architecture, you must follow the following procedure when upgrading a XenForo 2.2 installation that already has VaultWiki, or you will...
Click to expand...

Read the rest of this update entry...
 
pegasus updated VaultWiki with a new update entry:

4.1.10 Patch Level 1

(announced here: https://www.vaultwiki.org/articles/318/)

The relevant issues for XenForo:
  • Updated the expired SSL certificate when checking for new add-on updates
  • Significantly reduced the number of email subscription cancellation notifications sent when importing from another copy of VaultWiki
  • Fixed an issue where meaningless permissions keys could overrule expected permissions within the same database record
Click to expand...

Read the rest of this update entry...
 
@pegasus has released Vaultwiki 4.1.11PL4 (Security release)

A significant number of the issues disclosed below were identified by AI using an unknown prompt from a third-party and subsequently submitted to us via an appropriate reporting channel. Human developers then triaged that submission, verified individual issues, and created patches for them. These issues have been marked with the "[AI]" tag.

Summary​

The following classes of issues are addressed this month. Issues vary in difficulty, rarity, specificity, and severity. We have no evidence that any of these issues are known publicly or are actively being exploited. While some of the most serious-sounding issues tend to require that the database was already compromised in order to exploit, there are still a high number of other critical issues addressed.
  • Arbitrary Code Execution (1 issue - requires already-compromised database)
  • Arbitrary File Deletion (1 issue)
  • CAN-SPAM (2 issues)
  • Cross-Site Request Forgery (2 issues - require a user that can already achieve similar effects, by permission)
  • Data Loss (2 issues)
  • Denial of Service (5 issues)
  • HTML Injection (2 issues)
  • Information Disclosure (1 issue)
  • Local File Inclusion (2 issues - require already-compromised database)
  • Path Traversal (1 issue)
  • Permissions Escalation (13 issues)
  • Phishing (1 issue)
  • Remote Code Execution (1 issue - requires already-compromised database)
  • Server-Side Request Forgery (2 issues)
  • Stored Object Injection (1 issue - requires already-compromised database)
  • Subscription Management (1 issue)
  • Total: 38 issues (23 identified by AI)

We strongly recommend that all users running VaultWiki in a production environment update to a patched release.

Full article here:
 
Last edited:
@pegasus has released Vaultwiki 4.1.10PL5 (Security release)

A number of the issues disclosed below were identified by AI via a third-party and subsequently submitted to us via an appropriate reporting channel. Human developers then triaged that submission, verified individual issues, and created patches for them. These issues have been marked with the "[AI]" tag.

Summary​

The following classes of issues are addressed this month. We have no evidence that any of these issues are known publicly or are actively being exploited.
  • Cache Space Exhaustion (3 issues)
  • Cross-Site Data Exfiltration (1 issue)
  • Cross-Site Request Forgery (4 issues)
  • Denial of Service (3 issues)
  • Denial of Service Amplification (1 issue)
  • HTML Injection (1 issue - requires already-compromised database)
  • JavaScript Injection (1 issue)
  • Permissions Escalation (6 issues)
  • Remote Code Execution (1 issue - requires already-compromised database)
  • Spoofing (1 issue)
  • Time-of-Check to Time-of-Use (1 issue)
  • Upgrade Issue (1 issue)
  • Total: 24 issues (10 identified by AI)

VaultWiki - Wiki for Forum Communities - VaultWiki Security Update: July 2026

As of July 12, security patches for July 2026 are now available. Please note, this is an especially large patch, with changes to large numbers of files. A number of the issues disclosed below were identified by AI via a third-party and subsequently submitted to us via an appropriate reporting...
www.vaultwiki.org
 
You must log in or register to reply here.

Similar threads

Grimscythe
XF 2 [Paid] Looking for help with setting up an infobox and ambox for VaultWiki
Replies
1
Views
363
Alpha1
Alpha1
S
Add-on Need a Developer to Create Two Vaultwiki Plugins
Replies
2
Views
644
Alpha1
Alpha1
OakleyForum
Add-on PAID - Vault Wiki Modifications/Template Created
Replies
1
Views
1K
ForumCube
ForumCube
pegasus
Free VaultWiki and MediaWiki Import
Replies
2
Views
2K
pegasus
pegasus
Rizwan Kassim
  • Question Question
XF 1.1 Tried to install a plugin (VaultWiki) ,failed, homepage doesn't work now
Replies
6
Views
1K
pegasus
pegasus
Back
Top Bottom