Server action security considerations in NextJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary security benefit of Next.js server actions?

Server actions in Next.js run on the server side. What main security advantage does this provide compared to client-side code?

A They automatically encrypt all data sent to the client.

B They prevent exposing sensitive logic and secrets to the browser.

C They disable all user input to avoid injection attacks.

D They run faster because they use server hardware.

💡 Hint

Think about what code the user can see or modify in the browser.

Server actions keep sensitive code and secrets on the server, so users cannot see or change them. This reduces risks like exposing API keys or business logic.

❓ component_behavior

intermediate

What happens if a server action does not validate user input?

Consider a Next.js server action that processes form data but skips input validation. What is the most likely security risk?

A The server action will reject all requests without validation.

B The server action may crash due to unexpected input types.

C The server action will automatically sanitize inputs to prevent attacks.

D Malicious users could inject harmful data causing security issues like SQL injection.

💡 Hint

Think about what happens when bad data reaches the server unchecked.

Without validation, attackers can send harmful data that exploits vulnerabilities like SQL injection or cross-site scripting.

🔧 Debug

advanced

Identify the security flaw in this Next.js server action code

Review the server action below. What security issue does it have?

NextJS

export async function addUser(data) {
  await db.users.insert(data);
  return { success: true };
}

A It exposes the database connection string to the client.

B It uses synchronous code which blocks the server.

C It lacks input validation, allowing unsafe data to be stored.

D It returns sensitive user data in the response.

💡 Hint

Check if the data is checked before saving.

The function directly inserts user data without checking it. This can lead to storing harmful or malformed data.

📝 Syntax

advanced

Which server action code snippet correctly restricts access to authenticated users only?

Select the code that properly checks if a user is authenticated before proceeding in a Next.js server action.

A

export async function secureAction() {
  const user = await getCurrentUser();
  if (!user) throw new Error('Unauthorized');
  // action code
}

B

export async function secureAction() {
  if (user === null) return;
  // action code
}

C

export async function secureAction() {
  const user = await getCurrentUser();
  if (user === undefined) throw new Error('Unauthorized');
  // action code
}

D

export async function secureAction() {
  const user = getCurrentUser();
  if (!user) return 'Unauthorized';
  // action code
}

💡 Hint

Check for proper async usage and error handling.

Option A correctly awaits the async user fetch, checks for falsy user, and throws an error to block unauthorized access.

❓ lifecycle

expert

When is it safest to perform sensitive operations in Next.js server actions?

At what point in the server action lifecycle should you perform security checks and sensitive operations to ensure safety?

A Immediately after receiving the request, before any data processing.

B After processing data but before sending the response.

C During client-side rendering to reduce server load.

D Only after sending the response to the client.

💡 Hint

Think about when you can stop unauthorized requests early.

Performing security checks right after receiving the request prevents unauthorized or malicious actions early, saving resources and improving security.

Practice

1. Why should server actions in Next.js always check user authentication before proceeding?

easy

A. To allow client-side code to run faster

B. To speed up the server response time

C. To ensure only authorized users can perform sensitive operations

D. To reduce the size of the JavaScript bundle sent to the client

Solution

1. Step 1: Understand server action purpose

   Server actions run on the server to handle sensitive logic securely.

2. Step 2: Importance of authentication check

   Checking user authentication ensures only authorized users can access or modify protected data.

3. Final Answer:

   To ensure only authorized users can perform sensitive operations -> Option C

4. Quick Check:

   Authentication check = To ensure only authorized users can perform sensitive operations [OK]

Hint: Server actions protect sensitive logic by verifying users [OK]

Common Mistakes:

• Thinking authentication speeds up server response
• Confusing client-side speed with server security
• Believing authentication reduces bundle size

2. Which of the following is the correct way to define a server action in Next.js 14+?

easy

A. export async function actionName() { /* server code */ }

B. function actionName() { return Client }

C. const actionName = () => { console.log('client') }

D. export default function actionName() { return 'client' }

Solution

1. Step 1: Recognize server action syntax

   Server actions are async functions exported to run on the server.

2. Step 2: Identify correct export and async usage

   export async function actionName() { /* server code */ } correctly exports an async function for server action.

3. Final Answer:

   export async function actionName() { /* server code */ } -> Option A

4. Quick Check:

   Async export function = export async function actionName() { /* server code */ } [OK]

Hint: Server actions are async exported functions [OK]

Common Mistakes:

• Using client component syntax for server actions
• Missing async keyword in server action
• Not exporting the function

3. Given this server action code snippet, what will happen if the input is not validated?

export async function updateUser(data) {
  // No input validation
  await db.user.update({ where: { id: data.id }, data });
  return { success: true };
}

medium

A. The database may receive invalid or malicious data causing errors or security issues

B. The server will automatically reject invalid data

C. The client will validate data before sending, so no issues occur

D. The function will throw a syntax error

Solution

1. Step 1: Understand missing input validation

   Without validation, any data sent by client is accepted as-is.

2. Step 2: Consequences of no validation

   Invalid or malicious data can corrupt database or cause security vulnerabilities.

3. Final Answer:

   The database may receive invalid or malicious data causing errors or security issues -> Option A

4. Quick Check:

   Missing validation = risk of bad data [OK]

Hint: No validation risks bad data in database [OK]

Common Mistakes:

• Assuming server rejects invalid data automatically
• Believing client validation is enough
• Expecting syntax errors from bad input

4. Identify the security issue in this server action code and how to fix it:

export async function deletePost(postId) {
  await db.post.delete({ where: { id: postId } });
  return { deleted: true };
}

medium

A. Missing async keyword; fix by adding async to function

B. No return statement; fix by returning a success message

C. Incorrect database method; fix by using update instead of delete

D. Missing user authentication check; fix by verifying user identity before deleting

Solution

1. Step 1: Check for authentication or permission validation

   The code deletes a post without verifying if the user is allowed to do so.

2. Step 2: Fix by adding user identity check

   Before deleting, confirm the user is authenticated and authorized to delete the post.

3. Final Answer:

   Missing user authentication check; fix by verifying user identity before deleting -> Option D

4. Quick Check:

   Authentication missing = Missing user authentication check; fix by verifying user identity before deleting [OK]

Hint: Always check user permissions before data deletion [OK]

Common Mistakes:

• Ignoring authentication importance
• Confusing async keyword necessity
• Misunderstanding database method usage

5. You want to create a server action that updates user profile data only if the user is authenticated and the input is valid. Which approach best secures this action?

export async function updateProfile(user, data) {
  // What should you do here?
}

hard

A. Update database directly without checks for speed

B. Check if user is authenticated, validate data fields, then update database

C. Validate data on client only, then update database

D. Return success immediately and update database later asynchronously

Solution

1. Step 1: Verify user authentication inside server action

   Ensure the user object is valid and authenticated before proceeding.

2. Step 2: Validate all input data carefully

   Check each data field to prevent invalid or malicious input before updating the database.

3. Step 3: Update database only after passing checks

   Perform the update securely after authentication and validation.

4. Final Answer:

   Check if user is authenticated, validate data fields, then update database -> Option B

5. Quick Check:

   Authentication + validation = secure update [OK]

Hint: Authenticate user and validate input before DB update [OK]

Common Mistakes:

• Skipping server-side validation
• Relying only on client validation
• Updating DB without authentication