Server action security considerations in NextJS - Mini Project: Build & Apply

Server Action Security Considerations in Next.js

📋 What You'll Learn

💡 Why This Matters

🌍 Real World

Handling user input securely in web apps is critical to protect data and prevent unauthorized actions.

💼 Career

Understanding server action security is important for building safe Next.js applications and working with backend logic.

1

Set up initial form data

Create a constant called formData as an object with these exact properties: name set to an empty string, email set to an empty string, and message set to an empty string.

NextJS

# Your code here

Hint

Use an object with keys name, email, and message all set to empty strings.

2

Add a security token variable

Create a constant called securityToken and set it to the string "secure123" to simulate a token for validating server actions.

NextJS

const formData = {
  name: "",
  email: "",
  message: ""
};

# Your code here

Hint

Define a constant named securityToken with the exact string value "secure123".

3

Implement the secure server action

Write an async function called submitFeedback that takes a parameter data. Inside, check if data.token equals securityToken. If not, throw an error with message "Unauthorized". Otherwise, simulate saving feedback by returning { success: true }.

NextJS

const formData = {
  name: "",
  email: "",
  message: ""
};

const securityToken = "secure123";

# Your code here

Hint

Check the token inside the function and throw an error if it does not match. Return success if valid.

4

Complete the form component with server action

Create a React functional component called FeedbackForm that returns a <form> element with action={submitFeedback}. Inside the form, add hidden input with name="token" and value={securityToken}. Also add accessible labels and inputs for name, email, and message. Add aria-label="Feedback form" to the form.

NextJS

const formData = {
  name: "",
  email: "",
  message: ""
};

const securityToken = "secure123";

export async function submitFeedback(data) {
  if (data.token !== securityToken) {
    throw new Error("Unauthorized");
  }
  // Simulate saving feedback
  return { success: true };
}

# Your code here

Hint

Use a form with action set to the server action, include a hidden token input, and add accessible labels and inputs.

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