From 91d769441efe3d0a0323d23feb763a522025ca3f Mon Sep 17 00:00:00 2001
From: Nick Chomey <88559987+nickchomey@users.noreply.github.com>
Date: Wed, 28 Oct 2026 09:53:05 -0600
Subject: [PATCH 1/2] fix: resolve recorded db-path.php secret path for SQLite
 file operations

sqlite-database-integration 3.1 stores the database at a randomized path
recorded in FQDBDIR/db-path.php when nothing explicit is configured. Teach
get_sqlite_db_path() to consult that file after the explicit constants,
so file operations target the real database instead of a legacy path.
An explicitly configured DB_FILE takes precedence over the recorded path,
matching the drop-in, and a recorded :memory: database is refused like
the other in-memory configurations. Add a Behat scenario covering the
recorded secret path with a legacy decoy database.
---
 features/db-sqlite-path.feature | 39 +++++++++++++++++++++++++++++++++
 src/DB_Command_SQLite.php       | 24 +++++++++++++++++---
 2 files changed, 60 insertions(+), 3 deletions(-)

diff --git a/features/db-sqlite-path.feature b/features/db-sqlite-path.feature
index 37e7de1d..29dcffa6 100644
--- a/features/db-sqlite-path.feature
+++ b/features/db-sqlite-path.feature
@@ -61,6 +61,45 @@ Feature: Select the configured SQLite database for file operations
       |                 | selected.sqlite |        |                 |         |
       |                 |                 |        | selected.sqlite | /       |
 
+  Scenario: Resolve the recorded secret path from db-path.php
+    Given a WP install
+    When I run `wp eval 'mkdir( "recorded" ); copy( defined( "DB_PATH" ) ? DB_PATH : FQDB, "recorded/selected.sqlite" ); copy( "recorded/selected.sqlite", ".ht.sqlite" ); file_put_contents( "recorded/db-path.php", "<?php return " . var_export( getcwd() . "/recorded/selected.sqlite", true ) . ";" );'`
+    And I run `sqlite3 recorded/selected.sqlite "CREATE TABLE path_marker (value TEXT); INSERT INTO path_marker VALUES ('selected');"`
+    And I run `sqlite3 .ht.sqlite "CREATE TABLE path_marker (value TEXT); INSERT INTO path_marker VALUES ('other');"`
+
+    Given a paths.php file:
+      """
+      <?php
+      define( 'FQDBDIR', __DIR__ . '/recorded/' );
+      """
+    When I run `wp config set path_constants "require __DIR__ . '/paths.php'" --type=variable --raw`
+    And I try `wp eval 'echo "ready";'`
+    Then the return code should be 0
+
+    When I run `wp eval 'echo md5_file( ".ht.sqlite" );' --skip-wordpress`
+    Then save STDOUT as {OTHER_HASH}
+
+    When I try `wp db export selected.sql`
+    Then the return code should be 0
+    And the selected.sql file should contain:
+      """
+      INSERT INTO path_marker VALUES('selected');
+      """
+    And the selected.sql file should not contain:
+      """
+      INSERT INTO path_marker VALUES('other');
+      """
+
+    When I try `wp db drop --yes`
+    Then the return code should be 0
+    And the recorded/selected.sqlite file should not exist
+
+    When I run `wp eval 'echo md5_file( ".ht.sqlite" );' --skip-wordpress`
+    Then STDOUT should be:
+      """
+      {OTHER_HASH}
+      """
+
   Scenario Outline: Reject file operations on an in-memory SQLite database
     Given a WP install
     And an input.sql file:
diff --git a/src/DB_Command_SQLite.php b/src/DB_Command_SQLite.php
index b864bf19..344dcab0 100644
--- a/src/DB_Command_SQLite.php
+++ b/src/DB_Command_SQLite.php
@@ -83,10 +83,28 @@ protected function get_sqlite_db_path() {
 		$wp_content_dir = defined( 'WP_CONTENT_DIR' ) ? WP_CONTENT_DIR : ABSPATH . 'wp-content';
 
 		// Check for FQDBDIR and construct path.
-		$db_dir  = defined( 'FQDBDIR' ) ? FQDBDIR : $wp_content_dir . '/database';
-		$db_file = defined( 'DB_FILE' ) ? DB_FILE : '.ht.sqlite';
+		$db_dir = defined( 'FQDBDIR' ) ? FQDBDIR : $wp_content_dir . '/database';
 
-		$db_path = rtrim( $db_dir, '/' ) . '/' . ltrim( $db_file, '/' );
+		// DB_FILE selects a file inside FQDBDIR (sqlite-database-integration 3.1+).
+		if ( defined( 'DB_FILE' ) ) {
+			return rtrim( $db_dir, '/' ) . '/' . ltrim( DB_FILE, '/' );
+		}
+
+		// Check for the recorded secret path (sqlite-database-integration 3.1+).
+		$path_file = rtrim( $db_dir, '/\\' ) . '/db-path.php';
+		if ( file_exists( $path_file ) ) {
+			// phpcs:ignore WordPress.PHP.NoSilencedErrors.Discouraged -- Failure is checked below.
+			$recorded_path = @include $path_file;
+			if ( is_string( $recorded_path ) && '' !== $recorded_path ) {
+				if ( ':memory:' === $recorded_path ) {
+					WP_CLI::error( 'This command does not support in-memory SQLite databases.' );
+				}
+
+				return $recorded_path;
+			}
+		}
+
+		$db_path = rtrim( $db_dir, '/' ) . '/.ht.sqlite';
 
 		// If the file exists, return it.
 		if ( file_exists( $db_path ) ) {

From 2bff921a2d0a9b0c2df71a6767cba7c557ffca53 Mon Sep 17 00:00:00 2001
From: Nick Chomey <88559987+nickchomey@users.noreply.github.com>
Date: Wed, 28 Oct 2026 12:26:08 -0600
Subject: [PATCH 2/2] test(db-command): cover recorded path without loading the
 drop-in

---
 features/db-sqlite-path.feature | 33 +++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)

diff --git a/features/db-sqlite-path.feature b/features/db-sqlite-path.feature
index 29dcffa6..c6b6d930 100644
--- a/features/db-sqlite-path.feature
+++ b/features/db-sqlite-path.feature
@@ -100,6 +100,39 @@ Feature: Select the configured SQLite database for file operations
       {OTHER_HASH}
       """
 
+  @require-sqlite
+  Scenario: Resolve the recorded secret path without loading the drop-in
+    Given a WP install
+    When I run `wp eval 'mkdir( "recorded" ); copy( defined( "DB_PATH" ) ? DB_PATH : FQDB, "recorded/selected.sqlite" ); copy( "recorded/selected.sqlite", ".ht.sqlite" ); file_put_contents( "recorded/db-path.php", "<?php return " . var_export( getcwd() . "/recorded/selected.sqlite", true ) . ";" );'`
+    And I run `sqlite3 recorded/selected.sqlite "CREATE TABLE path_marker (value TEXT); INSERT INTO path_marker VALUES ('selected');"`
+    And I run `sqlite3 .ht.sqlite "CREATE TABLE path_marker (value TEXT); INSERT INTO path_marker VALUES ('other');"`
+
+    Given a paths.php file:
+      """
+      <?php
+      define( 'DB_ENGINE', 'sqlite' );
+      define( 'FQDBDIR', __DIR__ . '/recorded/' );
+      """
+    When I run `wp config set path_constants "require __DIR__ . '/paths.php'" --type=variable --raw`
+    And I try `wp eval 'echo "ready";'`
+    Then the return code should be 0
+
+    # Remove the drop-in so no DB_PATH or FQDB constant can be defined
+    # before get_sqlite_db_path() runs. Only the recorded-path branch can
+    # resolve this database.
+    When I run `rm wp-content/db.php`
+
+    And I try `wp db export selected.sql`
+    Then the return code should be 0
+    And the selected.sql file should contain:
+      """
+      INSERT INTO path_marker VALUES('selected');
+      """
+    And the selected.sql file should not contain:
+      """
+      INSERT INTO path_marker VALUES('other');
+      """
+
   Scenario Outline: Reject file operations on an in-memory SQLite database
     Given a WP install
     And an input.sql file: