Title: w3mypq
Author: axew3
Published: <strong>2026-06-02</strong>
Last modified: 2026-10-09

---

Szukaj wtyczek

![](https://ps.w.org/w3mypq/assets/banner-772x250.png?rev=3680140)

![](https://ps.w.org/w3mypq/assets/icon-128x128.png?rev=3559906)

# w3mypq

 Autor: [axew3](https://profiles.wordpress.org/axewww/)

[Pobierz](https://downloads.wordpress.org/plugin/w3mypq.3.2.6.zip)

 * [Szczegóły](https://pl.wordpress.org/plugins/w3mypq/#description)
 * [Recenzje](https://pl.wordpress.org/plugins/w3mypq/#reviews)
 *  [Instalacja](https://pl.wordpress.org/plugins/w3mypq/#installation)
 * [Rozwój](https://pl.wordpress.org/plugins/w3mypq/#developers)

 [Wsparcie](https://wordpress.org/support/plugin/w3mypq/)

## Opis

w3mypq provides a privacy-focused file encryption and sharing tool for WordPress.
Files are encrypted in the user’s browser before upload using ML-KEM and AES-GCM.

The plugin combines modern cryptographic standards with low-level binary packing,
thread isolation, and forensic memory management. Its low-overhead, browser-based
w3Gemini engine supports secure and fast post-quantum file sharing between users.

What you must know: This plugin aims to be a high-security tool that guarantees 
absolute data sovereignty by design. To achieve this, the plugin utilizes state-
of-the-art post-quantum cryptography. It is engineered so that even if the service
provider’s servers are compromised, attackers only find useless, encrypted data 
because nobody else possesses the users’ private decryption keys. This architecture
offers the highest level of security, assuming the integrity of the core cryptographic
code. The deployment must remain free from modifications that compromise private
keys or exploit payload structures via unauthorized public key injection and user
impersonation.

As a user, if you worry about a compromised server or a malicious administrator,
BPQ turns WordPress sites worldwide into a global, decentralized sharing network.
By using the standalone [BPQ](https://www.axew3.com/w3/bennypq/) client gateway 
loaded locally (and NOT served by WordPress), there is absolutely no way for a server-
side attacker to inject public keys or tamper with the code. Your keys and encryption
routines remain 100% secure. [Decentralized file sharing in WordPress](https://www.axew3.com/w3/2026/09/how-to-decentralized-file-sharing-in-wordpress/).

#### Features

 * Implements ML-KEM 1024 for post-quantum key encapsulation.
 * Supports ML-DSA 87 signatures for sender verification.
 * Utilizes AES-GCM-256 for symmetric file encryption.
 * Encrypts files locally in the browser before upload (Zero-Knowledge).
 * Supports sharing files with one or more recipients.
 * Displays the user’s daily upload quota and the remaining time until it resets.
 * Recipients decrypt files locally using their own private keys.
 * Guest mode for local-only encryption and decryption.
 * Designed around NIST post-quantum cryptography standards.

#### Admin Options

 * Maximum attachment file sizes configuration.
 * Daily user storage upload quota limits.
 * User role permissions access level controls.
 * Dynamic encrypted file retention storage periods.
 * Maximum unique recipients allowed per file.
 * Cryptographic Security Headers & Shields options.
 * Ghost Rider, a powerful and experimental PQ Server WordPress Shield.
 * The Vault Module Maintenance feature provides easy options to execute targeted
   administrative cleanup routines on the server or for testing purposes.

Manage all configuration panels by navigating to: WP Admin -> Settings -> w3mypq.

#### How to for users

 * [How to, Tips and FAQ](https://www.axew3.com/w3/wordpress-w3mypq-how-to-and-faq/)

#### Online example

 * [Online example](https://www.axew3.com/w3/w3mypq/)

## Instalacja

 1. Upload the plugin folder to the `/wp-content/plugins/` directory, or install it
    through the WordPress Plugins screen.
 2. Activate the plugin through the Plugins menu in WordPress.
 3. Add the shortcode `[w3mypq_short]` to a page or post.
 4. Open the page and use the interface to generate keys, encrypt files, and share 
    them with recipients.

#### Customization

To preserve customizations during updates:

 1. Copy the `w3mypq-custom` folder from the plugin directory into `/wp-content/plugins/`.
 2. Edit:

 * `w3mypq.css`
 * `w3mypq_body.html`
 * `w3mypq-common-display.js`
    1. The plugin automatically loads these files when present.
    2. If the custom files are not found, the default plugin files are used.

## Najczęściej zadawane pytania

### What’s BPQ Standalone Sharing Client Integration

BPQ (BennyPQ) is a standalone HTML file featuring a cross-compatible format with
the w3myPQ WordPress plugin, designed to perform various confidential tasks and 
verifications alongside w3myPQ.

 * [BPQ](https://www.axew3.com/w3/bennypq/)

### Client-Side Limitations & Server Capacity

The size of the files that can be encrypted depends entirely on the processor power
and RAM of the device running the browser. Remember, all file encryption and decryption
happen directly client-side within the browser. Furthermore, while you can easily
encrypt files to create a 500MB or even 1GB payload, you must also account for connection
speeds and the server’s capacity to handle uploading or downloading such large amounts
of data.

For pure, client-side, zero-dependency browser execution, the maximum realistic 
limit is around 1 GB to 1.5 GB (2026).

### What does this plugin do?

The plugin allows users to encrypt files locally in their browser before sharing
or storing them.

It supports post-quantum key encapsulation using ML-KEM and digital signatures using
ML-DSA. Encrypted files can be shared with recipients who decrypt them locally using
their own private keys.

### Share files with multiple recipients

Registered users can encrypt files for one or more recipients. Recipients receive
access information and can decrypt the files locally using their corresponding Private
keys once downloaded.

### Does the server store my private keys?

No.

Private keys are generated locally in the user’s browser and should be stored securely
by the user.

The server only stores information necessary for sharing encrypted content, such
as public keys and encrypted files.

### What are ML-KEM, ML-DSA, and AES-GCM?

ML-KEM and ML-DSA are NIST-standardized post-quantum cryptographic algorithms. ML-
KEM handles secure key exchange, and ML-DSA provides digital signatures and sender
verification.

AES-GCM is the symmetric encryption algorithm used to encrypt and decrypt the bulk
file data itself, ensuring high-speed authenticated encryption.

### What is guest mode? (no recipients)

Files are not uploaded to the server when no recipients are added or the user is
not logged in.

### What’s Cincia Keys Vault (Advanced Private Keys Obfuscation)

Unlike traditional key managers that simply encrypt Private keys into standard formats,
w3myPQ introduces a radical Zero-Knowledge Obfuscation System known as the Cincia
Keys Vault.

The Cincia keys code will read the secret phrase, isolate the 2 correct fragments
from 97 fakes, revert the changed bytes to their original state, and rebuild your
ML-KEM and ML-DSA private keys in secure memory. Once rebuilt, they are automatically
loaded into the proper input based on their type (KEM or DSA), so you do not have
to load them manually.

Access it on the Get Keys screen.

 * [Cincia keys vault](https://www.axew3.com/w3/2026/08/evolution-of-the-nest-hardening-post-quantum-keys-with-cinciakeys-v3-0/)

### How are the Noble and pqcrypto_compat libraries used?

The plugin includes a compiled version of the Noble post-quantum cryptography library
for ML-KEM and ML-DSA for the client side encryption.

 * [Noble](https://github.com/paulmillr/noble-post-quantum)

The plugin includes PHP Pure-PHP implementation of Post-Quantum Cryptography Algorithms
to perform ML-DSA 87 handshakes.

 * [pqcrypto_compat](https://github.com/paragonie/pqcrypto_compat)

### Where do I report security bugs found in this plugin?

[axew3.com](https://www.axew3.com)

or

You can report security bugs through the Patchstack Vulnerability Disclosure Program.
The Patchstack team help validate, triage and handle any security vulnerabilities.
[Report a security vulnerability.](https://patchstack.com/database/vdp/a1feae95-f00f-4be8-a573-e79d658998e5)

## Recenzje

Wtyczka nie ma jeszcze żadnej recenzji.

## Kontrybutorzy i deweloperzy

„w3mypq” jest oprogramowaniem open source. Poniższe osoby miały wkład w rozwój wtyczki.

Zaangażowani

 *   [ axew3 ](https://profiles.wordpress.org/axewww/)

[Przetłumacz wtyczkę “w3mypq” na swój język.](https://translate.wordpress.org/projects/wp-plugins/w3mypq)

### Interesuje cię rozwój wtyczki?

[Przeglądaj kod](https://plugins.trac.wordpress.org/browser/w3mypq/), sprawdź [repozytorium SVN](https://plugins.svn.wordpress.org/w3mypq/)
lub czytaj [dziennik rozwoju](https://plugins.trac.wordpress.org/log/w3mypq/) przez
[RSS](https://plugins.trac.wordpress.org/log/w3mypq/?limit=100&mode=stop_on_copy&format=rss).

## Rejestr zmian

#### 3.2.6

 * Release Date: 09 Oct 2026
    Fix: Update `wp-w3mypq.php` (and `w3mypq.js` ) to 
   check that the full payload does not exceed the remaining daily quota, so as 
   to prevent exhausting it unnecessarily, within the w3myPQ flow (previously only
   applied to BPQ endpoint). Note: If the `w3mypq.js` file is not updated due to
   browser caching, the `wp-w3mypq.php` code will fall back to its previous behavior,
   exhausting the user’s quota in the event of a large and then failed payload. 
   Security: Fix `function w3mypq_handle_incoming_rest_payload` on `wp-w3mypq.php`,
   avoid to send an empty metadata field to trigger a true match against an empty
   or expired database transient token. UI-Fix: Added server-response alert message
   handling to the Php send_emails callback inside `w3mypq.js`. Default theme: Set
   drawer element `.w3mypq-trigger` as – display:none; – by default into `w3mypq.
   css`.

#### 3.2.5

 * Release Date: 06 Oct 2026
 * Fixed: Updated wp-w3mypq.php to check from the very start that the BPQ payload
   does not exceed the $daily_quota, preventing the user’s daily quota from being
   prematurely exhausted.
 * Note: BennyPQ (BPQ) has been updated to the latest version, 3.2.6. This release
   adds an option to configure chunk size and allows loading an ML-DSA key from 
   any input, including the CinciaKeys Vault, into the Ghost Files Share panel. 
   See https://www.axew3.com/w3/bennypq/
 * Fixed: The interface hints for the BPQ Share Panel to make it clearer and simpler.
 * Various minor fixes across the entire plugin, including adjustments to the default
   w3mypq.css to properly display the entire CinciaKeys Vault on small screens, 
   and the w3mypq_body.html.
 * Fixed: Ghost Rider for a strict context-aware Privilege Escalation Wall that 
   forces an ML-DSA challenge whenever any request attempts a user role modification
   and the option is active.

#### 3.2.4

 * Release Date: 04 Oct 2026
 * Upgrade: Added dedicated option `Protect Admin Profiles` to toggle `Ghost Rider
   Server Shield` protection whenever an Administrator executes profile updates.
 * Fix: Prevented `Ghost Rider Server Shield` action triggers from locking out standard,
   non-administrative user profile saves.
 * Note about PQ shield: Should we add the Proactive Bootstrap File Integrity Scanner
   to check for hidden .user.ini malware drops next?

#### 3.2.3

 * Release Date – 02 Oct, 2026 *
 * Fix: Corrected `$daily_quota_mb` in wp-w3mypq.php to properly calculate the user’s
   Daily Storage Available value, which previously defaulted to 100MB on latest 
   3.2.1.

#### 3.2.1

 * Release Date – 01 Oct, 2026 *
 * Fix: The `wp-w3mypq.php` PHP codebase has been thoroughly cleaned up and optimized.
 * Fix: Corrected a missing `</div>` tag in `w3mypq_body.html` and stripped out 
   all `<br>` tags.
 * Fix: The `w3mypq.css` default file has been definitively resolved and finalized.
 * Fix: Option `w3mypq_server_shield` deletion upon plugin uninstall.
 * Note: The core template structure and default JavaScript codebase are now highly
   stable. The template is unlikely to change for a long (but very long) time. Remember
   to clear your browser cache.
 * Enjoy! Please report any bugs you find and feel free to contribute to improving
   the code in any way you can!

#### 3.2.0

 * Release Date – 30 Sep, 2026 *
 * Fix: Resolved an issue where the w3myPQ Shield would trigger even if deactivated.
 * Note: You will likely need to disable the w3mypq plugin to resolve this issue
   and then execute the update.
 * Fix: Resolved a code error on line 2527 inside the `wp-w3mypq.php` file regarding
   the dropzone text assignment: `document.getElementById('dropzone_text').innerText
   = file.name + " (" + file.size + " bytes)";`
 * Fix: Optimized the `w3mypq_handle_incoming_rest_payload()` (for the BPQ ghost
   file sharing) function in `wp-w3mypq.php` to ensure it correctly purges temporary
   payload files and folder from the `wp-content/uploads/w3mypq_staging/` folder
   using the native WP_Filesystem() and also in case of errors.
 * Fix: w3mypq.css and w3mypg_body.html remove some 
    tags.  tags will be removed
   all over on next 3.2.1 version.
 * Info: The wp-w3mypq.php PHP code will be optimized and all fixed on 3.2.1. Anyway
   it is fully working now.

#### 3.1.9

 * Release Date – 30 Sep, 2026 *
 * Note: This release, as promised, is all about the template layout.
 * Note: This new simplified and fixed template layout is not backward-compatible
   with previous versions. You must ensure that you load all new files and completely
   clear your browser cache.
 * Fix: All and any inline CSS styles injected by JavaScript (w3mypq.js and w3mypq-
   common-display.js) into the w3mypq_body.html file have been removed and refactored
   into dedicated classes. All classes have been added to the w3mypq.css file.
 * Fix: The w3mypq.css file has also been cleaned up and (quite) optimized, making
   it easier for anyone to customize the w3myQP tool as more like.
 * Change: The default w3myPQ theme now closely matches the native WordPress dashboard/
   front-end style. All layout colors can now be changed and overridden directly
   via the CSS file.
 * General: improvements made across all documentation hints, terminology, and instructional
   phrasing.

#### 3.1.8

 * Release Date – 28 Sep, 2026*
 * Fixed: Removed (the infamous) inline styles injected by JavaScript on pubKeyState
   and privKeyState elements when keys are loaded. The script now dynamically applies
   classes (.pubKeyStateLoaded, .privKeyStateLoaded, .pubKeyStateNOTLoaded, .privKeyStateNOTLoaded),
   which have been added to the w3mypq.css file.
 * Fixed: The default theme UI is currently under construction. Default colors have
   been subtly adjusted to better fit the native WordPress style. This is just an
   ongoing minor improvement.
 * Add: Ghost Rider, an experimental w3myPQ Server Shield Panel. Detailed documentation
   and explanations are available on the new dedicated sub-page. Please note that
   this feature operates completely independently and is not linked to the w3myPQ
   core scope. Be sure to READ all hints on that page BEFORE enabling this option.
 * Coming Soon: All inline CSS currently injected by JavaScript (ex in the Cincia
   Keys screen) will be refactored to use dedicated CSS classes. The Drawer icon(
   located at the bottom right of the Decrypt screen) will be completely rewritten.
   The CSS will be cleaned up.

#### 3.1.7

 * Release Date – 26 Sep, 2026*
 * Fixed: When the -Page URL for BPQ- option is leaved blank it completely disable
   the BPQ endpoint.
 * Security: Fixed an authentication bypass vulnerability affecting the chunked 
   multi-part REST API upload handler for BPQ.
 * Security: Hardened token-based validation tracking states inside the w3mypq incoming
   payload routing endpoints.
 * Fixed: Optimized UI rendering engine to suppress text rendering inside the Drawer
   for payloads exceeding 1 MB.
 * Fixed: Re-added the missing „Display in RAM or Download only” options to the 
   decryption screen. For this fix the file w3mypq-common-display.js has been updated.

#### 3.1.6

 * Release Date – 20 Sep, 2026*
 * Fix: Undefined array key „var_download_name” in wp-w3mypq.php on line 105
 * Fix: Patched media-src CSP array properties to permit local base64 video previews.
 * Fix: Hardened plugin activation rules to stop options auto-triggering on fresh
   installs.
 * Security option: Bundled zero-trust emoji CDN stripping into the CSP lockdown
   toggle, when Lockdown Content Security Policy (CSP) option is active.
 * Security option: Eliminated s.w.org background network requests to block domain
   injections, when Lockdown Content Security Policy (CSP) option is active.

#### 3.1.5

 * Release Date – 20 Sep, 2026*
 * Fix: Patched email link generation failures under Plain Permalinks and fixed 
   all others.
 * Upgrade: Added Custom GET Variables „Obscurity section” (see Admin panel)
 * Security: Allow admins to mask vault sharing links.
 * Note: The /js/w3myPQ.js file has been updated. Be sure to load the updated version
   and not the one cached by your browser.
 * Note: The BPQ standalone HTML client for w3myPQ includes this notice on the „
   How To” page: The WordPress permalink structure must not be set to „Plain” for
   BPQ file sharing to work.
 * Fix: Minor CSS fixes

#### 3.1.4

_Release Date – 18 Sep, 2026_
 * Add: Implemented secure validation gates for BennyPQ.
https://www.axew3.com/w3/bennypq/ * Add: Includes PHP Pure-PHP implementation of
Post-Quantum Cryptography Algorithms to perform ML-DSA BPQ/w3myPQ handshake. * Add:
Integrated native pure-PHP ML-DSA math loops for BPQ. * Fix: Add a preloader to 
the decryption screen to notify the user that a, maybe long, decryption task is 
running. * Fix: The wpautop() WP function p tags additions on DOM problem, using
two CSS rules into the w3mypq.css file. See https://www.axew3.com/w3/forums/viewtopic.
php?t=2195 * Fix: Correctly load keys and throw error if wrong formats. * Note: 
w3myPQ since this 3.1.4 version integrates natively with the cross-origin standalone
client application layer. * Download BPQ here: https://github.com/axew3/BennyPQ 
or here: https://www.axew3.com/w3/bennypq/ * Welcome to the era of true secret file
sharing.

#### 3.1.3

_Release Date – 02 Sep, 2026_
 * Fix: Implemented a 1 GB pre-flight size safety 
check across all encryption vectors (Folders, Files) to protect browser resources.*
Optimization: Refactored `w3zipFolder()` to loop directly over native browser file
pointers, completely eliminating the need for `Array.from()` memory allocations.*
Optimization: Integrated an instant `break` statement inside the file counter loop
to prevent thread freezes when users accidentally select massive multi-gigabyte 
folders. * Performance: Standardized the warning threshold to 1 GB across both single-
file and directory streams, optimizing execution safety for desktop and mobile sandboxes
alike. * Info: A complete how to and FAQ page will be available soon at: https://
www.axew3.com/w3/wordpress-w3mypq-how-to-and-faq/ * Add: activate preloader when
the folder encryption start. The template improvements are coming soon. * Fix: minor
fixes for the default file w3mypq_body.html.

#### 3.1.2

_Release Date – 01 Sep, 2026_
 * Fix: Dependency issue (3.1.0 bug) where the PHP
code would fail to load the new 0.7.1 Noble library and mistakenly load the old 
0.6.1 version. * Add: Added full, recursive local folder and subfolder support for
post-quantum encryption. * Add: Implemented an isolated background Web Worker compression
engine using pure Vanilla JavaScript with zero external dependencies or libraries.*
Performance: Optimized directory binary compilation using Zero-Copy Transferable
Objects to guarantee smooth UI execution with zero main-thread lag. * Security: 
Direct, seamless in-memory integration streaming packed folder archives directly
into the ML-KEM-1024 encapsulation handler. * NOTE: A new input element `<input 
class="buttonC" type="file" id="myFolderToBeCryptedMLKEM" name="myFolderToBeCryptedMLKEM"
webkitdirectory>` has been added to the standard `w3mypq_body.html` file. If you
are using a customized layout file, you must add this element manually to enable
folder encryption features. * Minor fixes.

#### 3.1.0

_Release Date – 30 Aug, 2026_
 * Update: Upgraded the Noble post-quantum cryptographic
library to the latest stable version 0.7.1. * Compatibility: Old existing ciphered
files remain (obviously) fully backward compatible with this update. * Technical
details: https://www.axew3.com/w3/forums/viewtopic.php?t=2189 * Remove: Removed 
the call to the public function `remove_html_and_js_comments($content)`. This function
was previously executed to prevent WordPress `wpautop()` from automatically injecting`
<p>` tags into the embedded default `w3mypq_body.html` file. This issue is now bypassed
by properly wrapping all HTML tags and comments inside container `<div>` elements,
into the `w3mypq_body.html`. * Note: The `w3mypq-custom/w3mypq_body.html` file explicitly
maintains all old original comments, return carriages, spaces, and formatting intact.

#### 3.0.9

_Release Date – 25 Aug, 2026_
 * Fix: CinciaKeys Vault has been upgraded to a new(
really) definitive version. While it maintains backward compatibility with 3.0.8,
users should deobfuscate old keys and obfuscate them again using the new, secure
3.0.9 CinciaKeys engine. * About: https://www.axew3.com/w3/2026/08/evolution-of-
the-nest-hardening-post-quantum-keys-with-cinciakeys-v3-0/ * Fix: Correctly cleaned
up the Decrypt panel when a new encryption occurs. * Add: Added automatic naming
for ML-KEM and ML-DSA private keys when they are created or rebuilt. * Fix: Minor
bug fixes throughout the application (excluding 'custom files’).

#### 3.0.8

_Release Date – 22 Aug, 2026_
 * Fix: hybridDecryptResults div panel correctly removed
when a new encryption occur. * Fix: Cincia keys vault: Custom Base-36 Obfuscation
Matrix: Upgraded the split engine to process fragments using an extended 36-character
alphabet (0-9 and a-x). This expands the character space and structural entropy 
of the obfuscated layers. Algorithmic Uniformity: Ensured that both real and fake
segments share the exact same Base-36 distribution, preventing static analysis from
identifying the genuine private key fragments inside the 97-row matrix. * NOTE: 
Old obfuscated Private keys will work (rebuilt) OK with this definitive Cincia keys
vault version. * NOTE: Users should perform a fresh **Split operation** on their
original post-quantum private keys using the upgraded v3.0.9 interface.

#### 3.0.7

_Release Date – 16 Aug, 2026_
 * Add: The Cincia Keys Vault, Available under the
Get key screen, check what it do here: https://www.axew3.com/w3/2026/08/cincia-keys-
vault-hide-private-keys/ * Change: If a signed ML-DSA file is decrypted without 
providing the public key, the system will mark the file as NOT VERIFIED. However,
if the ML-KEM key is valid, the decrypted content will be displayed. * Fix: Add '
uPrivateKeyMldsa’ into the 'function globalReset()’ on w3mypq.js. * NOTE: The /js/
w3mypq.js, w3mypq.css, w3mypq_body.html and w3mypq-common-display.js files may be
cached by your browser. Please ensure that you clear your browser’s cache if you
encounter console errors or if something is not working properly. * NOTE: If you
use the custom 'w3mypq_body.html’ or 'w3mypq.css’ or w3mypq-common-display.js files,
you must take into account that updates need to be applied. * HELP: To update your
layout to fit the new additions follow this topic: https://www.axew3.com/w3/forums/
viewtopic.php?t=2185

#### 3.0.6

_Release Date – 31 Jul, 2026_
 * Fix: Updated the w3mypq.js file to allow signing
in Guest mode (or when no recipients are added). * Add: Based on the Guest mode 
update, the „-Load Sender ML-DSA Public Key-” option has been added to the decryption
screen. * Fix: Corrected a mismatched HTML closing tag in `w3mypq_body.html` on `
<h2 class="h2EncryptedLoaded">Secure File Loaded</h3>`. * Note: The standalone w3myPQ
single-file HTML excerpt has been released. The BennyPQ tool and the w3myPQ WordPress
plugin now use a cross-compatible file format: https://www.axew3.com/w3/bennypq/*
Note: Support for uploading encrypted files to the w3myPQ WordPress plugin will 
be added in version 3.0.7.

#### 3.0.5

_Release Date – 01 Jul, 2026_
 * Fix: w3mypq.js file about: * Fix: Js – Resolved
a client-side clock synchronization glitch in w3RenderLiveDailyQuotaCountdown where
subsequent multi-recipient file encryptions would unintentionally trigger an execution
timeline shift back. * Fix: Js – Implemented a global window timestamp reference
guard (window.w3QuotaTargetEndTime) to lock the target destination expiration milestone
on first load, allowing middle-upload updates to refresh size metrics without disturbing
the running clock tracking track. * Fix: Js – Restructured the window.w3RefreshQuotaSizeText
closure scope loop to pull data values dynamically from live global configuration
object memory fields instead of static closure properties, guaranteeing immediate
frontend storage text alignment upon chunk completion handlers.

#### 3.0.4

_Release Date – 25 Jun, 2026_
 * Add: Options – administrative configuration switches
for Cryptographic Security Headers and Shields directly into the plugin settings.*
New: Enforced HTTP Strict Transport Security (HSTS) integration parameter to automatically
block protocol downgrade attacks and protect post-quantum public key transmissions.*
New: Targeted, site-wide compatible Content Security Policy (CSP) header framework
that restricts mobile/desktop script execution targets entirely to trusted local
assets and secure Web Workers.

#### 3.0.3

_Release Date – 24 Jun, 2026_
 * Critical: Security architecture upgrade. Due to
foundational cryptographic hardening, all files encrypted with version 3.0.2 or 
earlier are no longer compatible and cannot be decrypted by this version (3.0.3>).*
Fix: Resolved a calculation error in the rolling daily storage quota tracker where
the user usage transient computed incorrect totals. * Tweak: Cleaned up chunk-index
loop evaluations to ensure storage limits are applied accurately across all upload
sizes. * Fix: Activate the storage view drawer elements only when required. * Files:/
js/w3mypq.js and /js/worker.js * Fix: Standardized FIPS-204 signature context structures
to an explicit domain separation text layout string, introducing a strict policy
gatekeeper to drop signed payloads if sender public validation keys are omitted.*
Fix: Restored true thread-safe cryptographic verification on the Web Worker pipeline,
converting signature evaluations into explicit async object payload handshakes ({
buffer, isAuthentic }) to pass verified identity states cleanly to the frontend 
interface. * Fix: As 3.0.2 – implemented absolute AEAD integrity protection across
the envelope header, binding the recipient index metadata parameters directly into
the AES-GCM Additional Authenticated Data (AAD) block via zero-copy views to permanently
block unauthorized file-tampering or slot-swapping attacks. * Fix: Hardened multi-
recipient encryption arrays by wrapping the decapsulated ML-KEM-1024 shared secrets
inside a secure SHA-256 digest layer to eliminate master-key linear relationship
vulnerabilities. * Note: As of version 3.0.3, files encrypted in Guest mode (with
no recipients) should NOT be signed, or the „Personal” decryption will fail.

#### 3.0.2

 * Release Date – 21 Jun, 2026 *
 * Fix: Hardened binary file format against recipient-list metadata tampering using
   AES-256-GCM AEAD (Authenticated Associated Data).
 * Fix: Clarified misleading status explanations on alert notices.
 * Add: an help function so to mitigate the problem of the wpautop WordPress function.
 * See: https://wordpress.org/support/topic/3-0-0-template-problems/ to read applied
   solutions and helps.

#### 3.0.1

 * Release Date – 16 Jun, 2026 *
 * Fix: Implemented a definitive template fix by moving all front-end interface 
   and functionality JavaScript out of the HTML file and into a new dedicated script:`
   w3mypq-common-display.js`. This resolves the `wpautop` paragraph tag injections
   that were breaking script execution on specific themes.
 * See: https://wordpress.org/support/topic/3-0-0-template-problems/
 * Fix: Moved CSS styles and selectors previously injected via JavaScript directly
   into the `w3mypq.css` stylesheet.

#### 3.0.0

 * Release Date – 15 Jun, 2026 *
 * Fix: Resolved a legacy bug present since version 1.0.0 where Guest Mode failed
   due to an incorrect key loading sequence.
 * Fix: Fixed a security loophole where users could bypass daily limits and continue
   uploading files if the page was left open after the time limit elapsed, caused
   by a missing backend transient verification check.
 * Fix – Style: Performed a comprehensive cleanup of `w3mypq.css` and removed remaining
   unused selectors to establish the definitive, optimized default design.
 * Tweak: Moved the interface toggle JavaScript code from `w3mypg.js` directly to
   the bottom of `w3mypq_body.html`. The code has been shortened and optimized, 
   neatly containing the encryption, decryption, and key-generation interface elements
   inside their own wrappers for immediate clarity.
 * Important: This release completely rebuilds core files (`w3mypq_body.html` and`
   w3mypq.css`). It is not backward-compatible with older custom user templates.
 * Fix: Fixed a potential memory layout crash by adding validation guards to catch
   detached or empty `ArrayBuffer` data (0 bytes) before decryption begins.
 * Fix: minor fixes all around.

#### 2.3.2

 * Release Date – 12 Jun, 2026 *
 * Fix: Refactored plugin life-cycle hooks by moving the automated daily file cleanup
   cron scheduling out of the class constructor and into the global plugin activation
   scope. This ensures full validation compliance and eliminates performance overhead
   on standard page loads.
 * Fix: Optimized the `handle_encrypted_upload` and `get_bulk_public_keys` functions
   by removing redundant `get_option('w3mypq_options')` database calls to speed 
   up server processing.
 * Fix: all emoji icons entities.
 * Note: Please review the 2.3.1 changelog regarding the critical template layout
   rebuild changes.

#### 2.3.1

_Release Date – 07 Jun, 2026_
 * Fix – Style: Added notices for custom styles. *
Fix: Removed accidental `<style>` and `</style>` HTML tags from the external `w3mypq.
css` stylesheet. * Note: you should remove `<style>` and `</style>` HTML tags from
the custom w3mypq.css if using it. * Tweak: Moved CSS selector #w3_wrap_link-decrypt-
form from JS (w3mypg.js) into the stylesheet (w3mypq.css). * Fix: Performed initial
style cleanup and removed unused selectors from w3mypq.css to optimize file size.*
Add: Admin dashboard info panel displaying „Total Encrypted Vault Space Used”. *
Add: Added maximum file size display to the frontend „Upload Dynamic Quota & Countdown
Info Panel”. * Fix: Addressed minor codebase and styling bugs.

#### 2.3.0

_Release Date – 07 Jun, 2026_
 * Fix: Fix the new added 2.2.0 Vault Module Maintenance
Tools, Administrator buttons to execute targeted storage vault and transient purges(
preserving user keys) or full resets. * Add: Dynamic Quota & Countdown Info Panel
directly onto the front-end vault interface, utilizing a high-efficiency client-
side background ticker that updates every minute to display remaining storage capacity(
MB/KB) and a precise live hours/minutes countdown until the rolling 24-hour limit
resets. * Fix: Core uninstall execution mapping loops to automate immediate, complete
cleanup of all user meta data records, file tokens, background transient timeout
parameters, upload folders, upon plugin removal. * Fix: Reinforced server-side User
Quota Gatekeeper on the REST API endpoint, embedding an absolute hard-stop guard
that validates complete file dimensions on Chunk 0 and terminates unauthorized transmission
frames instantly. * Fix: Patched fractional mathematical chunk leaks on the REST
API gateway, enforcing a strict zero-tolerance hard stop block when daily bandwidth
thresholds are maxed out. * Fix: Discarded legacy un-sanitized profile meta save
routines to ensure wrong key inputs trigger an immediate native red warning alert
banner. * Fix: Post-Quantum key check. Fully automates Public key extraction directly
from pasted text, stripping out headers, whitespaces, and PEM boundaries.

#### 2.2.0

_Release Date – 06 Jun, 2026_
 * Add: Vault Module Maintenance Tools -into the Admin
panel settings page to execute targeted administrative cleanup routines on the server
vault storage footprint or for testing purpose. * Fix: Uninstall immediate complete
transients cleanup. * Add: A real-time, visual display placed right on the dashboard
to keep registered users informed of their remaining daily secure upload capacity
and the exact hour/minute countdown until their 24-hour quota limit resets. It auto
update each minute if the page is not reloaded. * Fix: user’s quota check. * Minor
fixes

#### 2.1.0

_Release Date – 04 Jun, 2026_
 * Add: 'Rolling Daily User Quota’ option to prevent
disk space exhaustion via fast WordPress transients. * Fix: Resolved an issue where
the 'link expired’ button would repeatedly reload the same page. * Fix: Minor bug
fixes and performance improvements.

#### 2.0.0

_Release Date – 02 Jun, 2026_

 * Note: this immediate major update to 2.0 version require to change custom HTML/
   CSS files is used.
 * Add: High-capacity file uploads processed seamlessly via an isolated binary slicing
   chunk loop.
 * Add: Dedicated administrative settings page managing maximum attachment sizes,
   user role permissions access gating, and dynamic file retention limits.
 * Fix: Send out email only when required.
 * Fix/Add: Migration of temporary tracking tokens to the high-performance WordPress
   Transients API instead of regular options.

#### 1.0.0

_Release Date – 02 Jun, 2026_

 * Initial public release.
 * ML-KEM support.
 * ML-DSA support.
 * Browser-based file encryption.
 * Multi-recipient sharing support.
 * Guest mode support.
 * Current version is subject to PHP upload limits imposed by the hosting environment.
 * Large-file upload optimization is planned for future releases.

## Meta

 *  Wersja **3.2.6**
 *  Ostatnia aktualizacja **5 dni temu**
 *  Włączone instalacje **Mniej niż 10**
 *  Wersja WordPressa ** 6.2 lub nowszej **
 *  Testowano do **7.1.3**
 *  Wersja PHP ** 7.4 lub nowszej **
 *  Język
 * [English (US)](https://wordpress.org/plugins/w3mypq/)
 * Tagi
 * [encryption](https://pl.wordpress.org/plugins/tags/encryption/)[file](https://pl.wordpress.org/plugins/tags/file/)
   [sharing](https://pl.wordpress.org/plugins/tags/sharing/)
 *  [Widok zaawansowany](https://pl.wordpress.org/plugins/w3mypq/advanced/)

## Oceny

Nie przesłano jeszcze żadnych recenzji.

[Twoja opinia](https://wordpress.org/support/plugin/w3mypq/reviews/#new-post)

[Zobacz wszystkierecenzje.](https://wordpress.org/support/plugin/w3mypq/reviews/)

## Zaangażowani

 *   [ axew3 ](https://profiles.wordpress.org/axewww/)

## Wsparcie

Zagadnienia rozwiązane w przeciągu ostatnich dwóch miesięcy:

     0 z 1

 [Zobacz forum wsparcia](https://wordpress.org/support/plugin/w3mypq/)

## Złóż datek

Czy chcesz wesprzeć rozwój wtyczki?

 [ Wspomóż wtyczkę ](http://www.paypal.me/alessionanni/)