ຄຳອະທິບາຍ
FirePhage Security helps you monitor WordPress security locally with malware scanning, official checksum verification, login protection, update visibility, and optional FirePhage dashboard connectivity.
FirePhage Security includes:
- local health and hardening checks
- WordPress core checksum verification
- plugin and theme repository integrity verification
- background malware scanning
- optional paid FirePhage dashboard connection for report sync and alerts
Licensing
FirePhage Security is licensed under GPLv2 or later.
All code and assets bundled inside this plugin are either:
- original FirePhage plugin files released under GPLv2 or later
- or GPL-compatible third-party assets documented below
Bundled third-party asset:
- Choices.js
- Source: https://github.com/Choices-js/Choices
- License: MIT
- Purpose: searchable country and continent dropdowns in the WordPress admin UI
- Copyright: Josh Johnson and contributors
Choices.js is distributed under the MIT License, which is GPL-compatible.
External services
This plugin can contact external services in three cases.
- Public checksum verification
By default, the plugin requests WordPress.org plugin and theme checksum metadata directly from WordPress.org.
If the site owner explicitly enables the optional FirePhage checksum cache in Scanner Settings or during first-run setup, the plugin requests the same checksum metadata from FirePhage first and then falls back to WordPress.org if needed. These requests send only the package type, slug, and version needed for checksum verification.
When you manually choose Compare or Restore for an official WordPress.org checksum mismatch, the plugin may request the matching reference file through FirePhage so it can show a file comparison or restore the official file you selected. This happens only after a user action and is not part of normal background scanning.
FirePhage is used as a retrieval layer for official WordPress.org reference files; the plugin does not execute arbitrary remote code.
Service: https://firephage.com
Privacy policy: https://firephage.com/privacy
Terms: https://firephage.com/terms
- Optional free FirePhage signature token
If the site owner explicitly requests a free FirePhage signature token, the plugin sends the chosen email address, site URL details, plugin version, and optional marketing-consent preference to FirePhage so the token can be emailed and remote signature updates can be enabled.
Service: https://firephage.com
Privacy policy: https://firephage.com/privacy
Terms: https://firephage.com/terms
- Optional paid FirePhage connection
If the site owner explicitly connects the plugin to FirePhage, the plugin sends site connection details and security reports to FirePhage so dashboard sync and alerting can work.
Service: https://firephage.com
Privacy policy: https://firephage.com/privacy
Terms: https://firephage.com/terms
ການຕິດຕັ້ງ
- Upload the plugin to
/wp-content/plugins/or install it through WordPress. - Activate the plugin.
- Open the FirePhage admin page to run local checks and scans.
ການຣີວິວ
ບໍ່ມີການຣີວິວສຳລັບປລັກອິນນີ້.
ຜູ້ຮ່ວມພັດທະນາ ແລະ ຜູ້ພັດທະນາ
“FirePhage Security” ແມ່ນຊອຟແວໂອເພັນຊອດ (Open Source). ບຸກຄົນຕໍ່ໄປນີ້ໄດ້ມີສ່ວນຮ່ວມໃນການພັດທະນາປລັກອິນນີ້.
ຜູ້ຮ່ວມພັດທະນາ
ແປ “FirePhage Security” ເປັນພາສາຂອງເຈົ້າ.
ສົນໃຈຮ່ວມພັດທະນາບໍ່?
ເບິ່ງລະຫັດ, ກວດເບິ່ງ ຄັງເກັບ SVN, ຫຼື ຕິດຕາມ ບັນທຶກການພັດທະນາ ຜ່ານ RSS.
ບັນທຶກການປ່ຽນແປງ
0.1.3
- Automatically refreshes local baselines for unverifiable plugin and theme package files when the installed package version changes.
- Separates official WordPress.org checksum mismatches from local baseline-only package changes in scan summaries and alert emails.
- Clarifies local baseline findings so premium plugin and theme updates are less likely to look like core tampering.
0.1.2
- Added an automatic full edge-cache purge trigger when public WordPress content is published or updated on connected FirePhage sites.
- Confirmed compatibility with WordPress 7.0.
0.1.1
- Moved brute-force attempt and lockout tracking out of a hot
wp_optionsrow into dedicated custom database tables. - Added automatic table creation and legacy state migration during plugin activation and upgrades.
- Reduced heavy database rewrites and MySQL binary log growth under login and bot traffic.