WP Uptime WP Registry grade B. Medium-severity findings · 2 findingsWP RegistryMedium-severity findings · 2 findingsOpen the reportB

Medium-severity findings.

Audited release

3.0.1

Findings

2

Worst severity

medium

Content hash

e3dcfb3fe69d35250b4c9048… Copy

Findings

• medium flush_rewrite_rules on every init causes avoidable DoS/load

  dos

  wpUptimeFeed hooks init, registers a feed, then calls $wp_rewrite->flush_rules() unconditionally on every request. Flushing rewrite rules writes options and regenerates rules — expensive and can degrade or lock the options table under traffic. Endpoint path/response come from options (admin Settings API). Observable: high load / options autoload churn with plugin active.

  wp-uptime.php:36-42

  Recommendation

  Flush only on activation/settings save when the path changes, never on init.

• low Version mismatch: slug wp-uptime-4.0.0 vs header 3.0.1

  version_mismatch

  Distribution folder/slug suggests 4.0.0 but plugin header Version is 3.0.1 (hashes version 3.0.1).

  wp-uptime.php:14-14

  Recommendation

  Align release tag, folder, and header Version.

WP Registry hashes the installable build and reports on that exact bytes-for-bytes copy. Embargoed findings are withheld until they are disclosed, so a clean verdict means nothing public is outstanding. WP Manifest does not audit code itself.